avastdaemon.log out of control

[specimen9999]

This file is currently 205 MB and is constantly writing things like:

Code: [Select]

Sat Dec  7 16:45:51 2013 [SESSION 2953850880]: Command 'POP' received.
Sat Dec  7 16:45:56 2013 [SESSION 2954915840]: Command 'SCAN' received.
How can this behaviour be turned off?

[specimen9999]

*bump*

[specimen9999]

The avast! team has nothing to say on this topic? A 200 MB log file that is constantly writing and has no way of turning off is nothing consider?

[specimen9999]

*bump*

[mustang64]

Hi There,
I don't think you will get an answer.  I would like to see a response to this problem as well.

It seems like they just IGNORE what is not working...I have said before no one even gives a darn so what is the purpose of this forum is what I would like to know...

Good Luck with the problem!

~Vern~

[krahulik]

Hi,
  well, there's not much to say to that - it is a bug of design. Right now we are in a process of this component rewrite from the scratch, in the avast version 9.0 it will be logging much less and standartly to the system log.

Currently it is possible to limit the amount of logged information by editing of /Library/Application Support/Avast/files/com.avast.daemon.plist: Set value of a parameter '-m' to 0x00000000 and reboot.

Best Regards,
Martin

[specimen9999]

Hi,
  well, there's not much to say to that - it is a bug of design. Right now we are in a process of this component rewrite from the scratch, in the avast version 9.0 it will be logging much less and standartly to the system log.

Currently it is possible to limit the amount of logged information by editing of /Library/Application Support/Avast/files/com.avast.daemon.plist: Set value of a parameter '-m' to 0x00000000 and reboot.

Best Regards,
Martin

Thank you Martin, that's all I needed to know!