Dear Philip

refer to your clamd.conf the user of clamav must be change to "qscand" not "qscend" and then you must change permisson of the directory "/var/log/clamav" and "/var/lib/clamav to qscand
for example "chown -R qscand:qscand /var/log/clamav"
and logrotate.d that I answer in
http://lurker.clamav.net/message/20050816.011551.5bacee6e.en.html

Best regards

Tawee Moonton
KOL Net Co. Ltd
Tel: +66-4-434-2888
Mobile: +66-9-213-7584
http://www.kol.co.th/
[EMAIL PROTECTED]
Thailand

----- Original Message ----- From: "Philip Craig" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, September 08, 2005 8:41 AM
Subject: [Clamav-users] Clamav 0.86-2 Freshclam permissions and log files


Hello Everyone,

I am attempting to set up ClamAV and have managed to install the rpm for
0.86.2 from ftp dot suse dot com. ClamAV seems to be up and running, yippee!
However, I have a problem with freshclam.  I set the user and log file
locations according to the qmailrocks dot org website ie user is "qscend"
and log file is /var/log/clamav/clam-update.log.

If I run "freshclam" it seems to connect and update but if I run
"freshclam -d" or "freshclam -i /var/log/clamav/clam-update.log", I get the
following error:

"ERROR: Can't open /var/log/clamav/clam-update.log in append mode (check
permissions!).
ERROR: Problem with internal logger."

I have tried changing the directory and file ownership to root as well as
qscand. I have changed the permissions to everything from 600 to 777 and
still I get the same error.

I have also noted that in the clam.log file, there is an error as follows:

"ERROR: Can't save PID in file /var/lib/clamav/clamd.pid"

In /var/lib/clamav there is no clamd.pid file!

Could these issues be related? Any suggestions?

In case you haven't guessed from the download site, I have installed this on
SuSE 9.1 Pro.
.
Philip Craig

_______________________________________________
http://lurker.clamav.net/list/clamav-users.html



_______________________________________________
http://lurker.clamav.net/list/clamav-users.html

Reply via email to