Kurt Albershardt wrote:
[snip]
> lsof -p `pidof clamd`
> lsof: no process ID specified
Clamd is not running.
[snip]
> 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?)
No. But that's the name used in the manual, freshclam.log is the default in the
configuration file... probably a previous installation used the instructions on
the manual.
Was clamav installed using emerge?
The first thing to check is Rob's suggestion, you may have a second clamav
installation perhaps in /usr/local/{bin, sbin, etc}.
> # 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
What about /etc/freshclam.conf?
> From clamd.conf:
>
> LogFile /var/log/clamd.log
> LogTime
> #LogSyslog
> PidFile /var/run/clamd.pid
> LocalSocket /tmp/clamd
> FixStaleSocket
Looks OK, but the startup script is not starting clamd, so you'll have to check
that script.
> 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...
This confirms that freshclam is run as a daemon by that script, that's what you
saw with ps. You'll have to disable the cron job.
To see what happens with clamd try to duplicate what the script does to start
it.
--
René Berber
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
