Hi,
I seem to be having some issues with clamav at the moment. It only seems to be creating the socket file on a reboot. If it gets restarted any other time, I get no socket file and then exim won't talk to it.
Anyone have any ideas?
I'm running the following versions of clam (on debian):
ii clamav 0.90.1-3etch7 antivirus scanner for Unix ii clamav-base 0.90.1-3etch7 base package for clamav, an anti-virus utili ii clamav-daemon 0.90.1-3etch7 antivirus scanner daemon ii clamav-freshclam 0.90.1-3etch7 downloads clamav virus databases from the In ii clamav-testfiles 0.90.1-3etch7 use these files to test that your Antivirus ii libclamav2 0.90.1-3etch7 virus scanner library
Thanks,
David
On Tue, Sep 11, 2007 at 10:08:04AM +0100, David Reynolds wrote:
Hi,
I seem to be having some issues with clamav at the moment. It only seems to be creating the socket file on a reboot. If it gets restarted any other time, I get no socket file and then exim won't talk to it.
Can we have an ls -lad /path/to/directory/holding/socket, preferably the backend of the clam log when it's restarted (maybe in daemon.log or mail.log), the default permissions of the socket...
Err, I think that'd be enough debug info to start with :)
(Otherwise we're just on speculation!)
Oh, one other question, does it still start it's networking side up? i.e. can you connect to the daemon over TCP/IP?
Cheers,