Kurt Albershardt wrote:
I'm not able to see a socket created, either when I use /var/tmp/clamav or when I configure as /var/run/clamav/clamd.sock (after creating the clamav directory and changing permissions appropriately.)
Try: lsof -p `pidof clamd`
lsof -p `pidof clamd` lsof: no process ID specified
And since there's no socket or pid created (despite options calling for such) I don't see anything in ps:
# /etc/init.d/clamd status
* status: started
# ps -fade|grep clam
clamav 7046 1 0 Apr11 ? 00:00:00 /usr/bin/freshclam -d -c 2 -l /var/log/clam-update.log
root 19482 18678 0 11:48 pts/0 00:00:00 grep clam
first look at the log, it should be in /var/log/clamd.log but it could be somewhere else (even syslog or disabled) depending on your clamd.conf (LogFile ..., LogSyslog ... LogVerbose).
Just a zero-length log file from clamd, and freshclam logs in two different places depending on whether it's called from clamd or from the cron job. Cron job logs where the config file specifies, but when clamd calls freshclam on startup, it uses clam-update.log (which I don't find mentioned in any of the config files or in the startup script--is it hardcoded?)
# ls -l /var/log total 10135 -rw-r--r-- 1 clamav clamav 5117 Apr 12 11:52 clam-update.log -rw-r--r-- 1 clamav clamav 0 Apr 11 20:21 clamd.log drwxr-xr-x 2 root root 48 Nov 2 23:21 cups -rw-rw---- 1 portage portage 229815 Apr 12 11:45 emerge.log -rw-r--r-- 1 clamav clamav 39 Apr 11 20:18 freshclam.log
From freshclam.log:
UpdateLogFile /var/log/freshclam.log
From clamd.conf:
LogFile /var/log/clamd.log LogTime #LogSyslog PidFile /var/run/clamd.pid LocalSocket /tmp/clamd FixStaleSocket
BTW, when starting/stopping clamd, I see a notification for freshclam only:
# /etc/init.d/clamd start [ ok ]ing freshclam... # /etc/init.d/clamd stop [ ok ]ing freshclam...
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
