After successful upgrading to clamav-0.9, and restarting the process, I got this error:
* Stopping clamd ... [ ok ] * Stopping freshclam ... [ ok ] * Starting clamd ...
Running as user clamav (UID 103, GID 1004)
ERROR: Can't open /var/log/clamav/clamd.log in append mode (check permissions!).
ERROR: Problem with internal logger. Please check the permissions on the /var/log/clamav/clamd.log file.
* Failed to start clamd [ !! ] * Starting freshclam ... [ ok ]
After issuing this command as root:
chown clamav /var/log/clamav/clamd.log
everything starts as expected - no errors.
Please update the ebuild, so it won't require manual ownership change.
The ebuild doesn't create the log at all. If you ended up w/ wrong permissions, you'll have to fix those yourself, since it's not an ebuild fault.
(In reply to comment #1)
> The ebuild doesn't create the log at all. If you ended up w/ wrong permissions,
> you'll have to fix those yourself, since it's not an ebuild fault.
First of, after the installation, I have this file. Therefore I assume that it is created by emerge.
Second, the clamd program runs from the account of clamav, that is also created by the ebuild. However the ownership of the file was "root".
And third, it is not about the permission. It is an ownership issue.
Simple "chown" at the end of "emerge" would fix it.
Kindly read the ebuild; it doesn't create any such log, so it's none of it's business to fix your broken permissions.
(In reply to comment #3)
> Kindly read the ebuild; it doesn't create any such log, so it's none of it's
> business to fix your broken permissions.
Well, the log file might be already in the tarball as empty file.
And I didn't see anything on the clamav.org installation manual about issuing such a command, which means that something is not right here...
Or maybe the manual install requires to have such a user before you install the packet.
I will re-read the doc, and post a comment.
There is nothing in the installation manual about this.
Maybe they just assume that people will install the packet from the "clamav" account?
Anyway, hopefully somebody can benefit from such change...
We are not changing permisssion of files that don't exist by default, hard to understand? The ebuild doesn't install them, so it won't change their permissions either.