|
|
Rank: Advanced Member
Groups: Member
Joined: 5/15/2009
Posts: 69
|
I think the current implementation of A2 Logs is really annoying (bold understatement actually).
When I click on "Logs" it starts showing the oldest entries, then keeps adding a single (little bit more recent) entry on top (and scrolling the others down) until minutes later (!) the most recent entry is finally shown.
Why is this implementation chosen? Why are not all entries shown at once?
A workaround might be to delete older entries regularly. However, I would like to save them before doing that. I see no option for saving logs. How do I do that?
We are one, but we are not the same... Talk to each other!
|
|
Rank: Advanced Member
Groups: Member, Moderation
Joined: 2/24/2006
Posts: 4,495
Location: Australia
|
Hi XIII,
If the size of the Logs are not restricted they are indeed can have a a lot of records.
When you are invoking the review of the the Log, nothing can be done by the program as to read all of them first.
If the number of logged events is not restricted it takes time.
The output is displaying entries as soon as each was read.
It can be implemented as you said, so all are “shown at once” , but in this case there will be just a big delay, which most likely "will not be “appreciated” as well 
At the same time, the described symptom of scrolling long output happens only upon the 1st time you asked the program to show huge Log.
Next time that area is accessed – the output is instant.
Can you confirm that, please?
XIII wrote:A workaround might be to delete older entries regularly Yes, and the other one that I mentioned above - reducing the total number of logged entries;
XIII wrote: However, I would like to save them before doing that. I see no option for saving logs.
I do agree with you and that can definitely be included into the Wish List.
I hope the developers will respond.
Actually, requests like this were implemented by users' request in the past
The example would be - “Save quarantine list” feature.
So let's hope the attitude towards all lists available will be similar, because that indeed helps, when something has to be remembered and/or investigated
My regards
XP Pro, SP3 (32-bit); a2-Free 4.5.0.21(beta); Firewall: Comodo CIS (Defense+ HIPS); Software DEP: integrated into Firewall; Anti-Malware: Mamutu 2.0.0.23 (beta); Verification Engine PlugIn (resident); AntiVirus: AVG Free (guard resident); SpyBot SD (+TeaTimer resident)
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/15/2009
Posts: 69
|
Lynx wrote:At the same time, the described symptom of scrolling long output happens only upon the 1st time you asked the program to show huge Log.
Next time that area is accessed – the output is instant.
Can you confirm that, please?
Unfortunately not.
I just had a look at it (PC was not switched off since I posted) and it starts scrolling from the oldest date again.
We are one, but we are not the same... Talk to each other!
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/15/2009
Posts: 69
|
Lynx wrote:It can be implemented as you said, so all are “shown at once” , but in this case there will be just a big delay, which most likely "will not be “appreciated” as well
To be honest: I seriously doubt that.
Many programs can load much larger data sets much faster.
I really think the way the logs are displayed is causing this gigantic delay.
We are one, but we are not the same... Talk to each other!
|
|
Rank: Advanced Member
Groups: Member, Moderation
Joined: 2/24/2006
Posts: 4,495
Location: Australia
|
Thanks for reply, XIII.
What Log precisely is always refreshing/scrolling?
The biggest one here is Malware IDS one and I cannot see that happening within one windows session
or
if that is within current session I have to Shutdown Mamutu and restart it in order to get that behaviour ... again, it happens just the 1st time I will go into the Logs
My regards
{added} I didn't see that you added another post regarding displaying lists implementation. We my ask developers,
but it could be just a behaviour of the 3rd party Grid Conlrol they are using,
if so - that may require finding another Conrol and make programing changes with all consequences ... not that it is impossible, but it may take time
(I used different Grids and some of them are slow indeed)
XP Pro, SP3 (32-bit); a2-Free 4.5.0.21(beta); Firewall: Comodo CIS (Defense+ HIPS); Software DEP: integrated into Firewall; Anti-Malware: Mamutu 2.0.0.23 (beta); Verification Engine PlugIn (resident); AntiVirus: AVG Free (guard resident); SpyBot SD (+TeaTimer resident)
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/15/2009
Posts: 69
|
Lynx wrote:What Log precisely is always refreshing/scrolling?
The biggest one here is Malware IDS one
That's the one.
Can't repeat it right now. A2 hangs on the log of 3-9-2009...
EDIT: Oh, now it continues scrolling...
We are one, but we are not the same... Talk to each other!
|
|
Rank: Advanced Member
Groups: Member, Moderation
Joined: 2/24/2006
Posts: 4,495
Location: Australia
|
Hi XIII,
Thanks for reply and confirmation - yes, that's the one
The biggest contribution to the said Log are made by those components that were Allowed, but left for monitoring.
Actually we can have very limited set of of those allowed Application if you look into the Rules.
At the same time, despite we trust the application, it's being monitored just in case “specific activities” occur.
As it's implemented now every time such trusted Application was invoked – there is a record.
So basically, in addition to what was written about restricting the number of records /deleting old records / clearing the list
probably it is possible to ask developers for having an option to suppress such loggings unless indeed “unexpected / specific” behaviour was intercepted (Wish List)
My regards
XP Pro, SP3 (32-bit); a2-Free 4.5.0.21(beta); Firewall: Comodo CIS (Defense+ HIPS); Software DEP: integrated into Firewall; Anti-Malware: Mamutu 2.0.0.23 (beta); Verification Engine PlugIn (resident); AntiVirus: AVG Free (guard resident); SpyBot SD (+TeaTimer resident)
|
|
Rank: Advanced Member
Groups: Member, Moderation
Joined: 2/24/2006
Posts: 4,495
Location: Australia
|
Hi XIII,
Current beta update fixed the problem.
The output of the Log entries in question are instant now
I purposely haven't clean the log content.
Cheers!
XP Pro, SP3 (32-bit); a2-Free 4.5.0.21(beta); Firewall: Comodo CIS (Defense+ HIPS); Software DEP: integrated into Firewall; Anti-Malware: Mamutu 2.0.0.23 (beta); Verification Engine PlugIn (resident); AntiVirus: AVG Free (guard resident); SpyBot SD (+TeaTimer resident)
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/15/2009
Posts: 69
|
I don't have the beta option enabled, but I guess it will get final soon?
We are one, but we are not the same... Talk to each other!
|
|
Rank: Advanced Member
Groups: Member, Moderation
Joined: 2/24/2006
Posts: 4,495
Location: Australia
|
XIII wrote:I don't have the beta option enabled, but I guess it will get final soon?
It sure will get into stable, but I don't have info about the time.
There are usually several improvements are made and has to be tested thoroughly.
My regards
P.S. I sent PM to you in the new forum regarding the matter
XP Pro, SP3 (32-bit); a2-Free 4.5.0.21(beta); Firewall: Comodo CIS (Defense+ HIPS); Software DEP: integrated into Firewall; Anti-Malware: Mamutu 2.0.0.23 (beta); Verification Engine PlugIn (resident); AntiVirus: AVG Free (guard resident); SpyBot SD (+TeaTimer resident)
|
|
|
Guest User |