On Thu, Jun 26, 2008 at 06:28:54AM -0700, metamorph said:
> Restarted clamd:
>  /etc/init.d/clamav-daemon restart
>  * Stopping ClamAV daemon clamd                                          [
> OK ] 
>  * Starting ClamAV daemon clamd  
> 
> Checked to see if anything changed:
> ps ax | grep [c]lamd
>  5514 ?        Ss     0:02 /usr/sbin/clamd
> 11815 ?        Ss     0:02 /usr/sbin/clamd

It looks like your earlier 'clamd restart' overwrote the pidfile used to
kill clamd, so the wrong one was killed.  run
kill 5514 11815

make sure they're dead (ps)

Test whether you actually have the option enabled:
clamconf | grep TCPSocket

If not:
dpkg-reconfigure -plow clamav-base

then:
/etc/init.d/clamav-daemon start

and 
netstat -plant

to verify that it is listening on 3310

> Any other suggestions on what to check or something else I need to change?
> I really appreciate your help.

Not trying to be disparaging, but do you have anyone local you can turn
to for support?  It seems like you might be a bit over your head, both
with basic system administration and with clamav.  I can help as I have
time, but it seems like you might need some help in other areas as well
that aren't completely appropriate for the clamav lists.
-- 
 --------------------------------------------------------------------------
|  Stephen Gran                  | Drinking makes such fools of people,    |
|  [EMAIL PROTECTED]             | and people are such fools to begin      |
|  http://www.lobefin.net/~steve | with, that it's compounding a felony.   |
|                                | -- Robert Benchley                      |
 --------------------------------------------------------------------------

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to