the common "ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log)."

[Len Conrad]

freshclam.conf has:

UpdateLogFile /var/log/clamav/freshclam.log

the file:

-rw-r-----  1 clamav  clamav  0 Jul 24 14:25 /var/log/clamav/freshclam.log

the directory:

/var/log/clamav

... is owned by clamav:clamav


clamd.conf has:

User clamav



there is no freshclam process already in memory


Those are all the points I found on Google.


I have another machine setup the same way (almost, using FreeBSd
ports) that worked first/every time.

suggestions?

Len


_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

[David F. Skoll]

Len Conrad wrote:

> suggestions?

Don't log to a file.  Log to syslog instead.  If it were up to me,
I'd remove the ability to log to a file and insist that everyone
use syslog.  There's really no point in the ClamAV team reinventing
syslog badly.

(I understand this is not possible because of Windoze portability
issues.  What a shame.)

Regards,

David.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml