Jim Maul said: > Let me attempt to clear up any confusion (and hopefully put this thread > to rest) by saying that I personally am not having any problems with > clamav and i am not experiencing the logging issue that actually started > this thread. I do and always have run clamav as qscand. My clamav logs > are owned by qscand and everything works great. I simply joined the > conversation somewhere in the middle because something caught my > attention. The fact that clamav creates its log file as root if it > doesnt already exist. Why create it at all if you cant write to it? > Its just silly.
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. > > Im anal as well which is why i stated that one should not tell anything > to log to / or /var/log directly for that matter. I like to have all > programs logging in their own directories under /var/log/. clamav is > /var/log/clamav/ apache is /var/log/apache/ and so on. That was the > basis for my SHOULDNT statement above. And it's a good idea. Especially if you don't start clamd as root. dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
