On Mon, 12 Jul 2010, noob wrote:
I do not use freshclam.log and instead have freshclam configured to log
via syslog.
I could try that if it would help...currently in my configuration file I
have:
UpdateLogFile /var/log/clamav/freshclam.log
Would I comment that out and use
LogSyslog yes ?
FWIW: I followed the above and now Freshclam is not generating the errors,
and seems to be updating.
I changed the clamd.conf to point back to /var/log/clamd.log, but I'm still
getting append permissions errors in System.log when clamd tries to run.
Clamd.log is owned by _amavisd:wheel.
Are you using amavisd? You mentioned ASSP. I have no knowledge of ASSP
other than what a quick search turned up.
I believe the clamd.log should be owned by whatever user clamd is running
as. On my system, that's _amavisd so clamd.log is owned by _amavisd.
So what user is running clamd? In Terminal, type ps -efw | grep clamd. On
my system, I get:
83 356 1 0 3:59.34 ?? 25:06.55 /usr/local/sbin/clamd
The 83 is the user owning this process. Then find out what user that is by
typing: grep 83 /etc/passwd (substitute whatever number you see for 83 -
if you do see 83, then it is _amavisd as the _amavisd account is
preconfigured on OS X as account number 83). I get:
_amavisd:*:83:83:AMaViS Daemon:/var/virusmails:/usr/bin/false
As you can see, we find that 83 is indeed _amavisd.
Then set the ownership on clamd.log to whatever owner you found and see if
that works.
-- Larry Stone
[email protected]
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
