Jim Maul said:
<SNIP>
That doesn't happen if you start it as the run-as user. It happens if you start it as root. That is why I say this "bug" is not necessarily a bug, but an administrative issue.
This was the key piece to the puzzle that i was missing. From the posts of the people who are actually having this problem, it was not immediately obvious that this ONLY happens when you run clamd as root. I was under the impression that the log file was created as root regardless of the user statement in clamd.conf. My apologies.
-Jim
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
