Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 87579 - Clamav-milter cannot start if the old socket is not manually deleted
Summary: Clamav-milter cannot start if the old socket is not manually deleted
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Antivirus Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-01 09:33 UTC by Robert
Modified: 2005-06-06 05:55 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert 2005-04-01 09:33:33 UTC
In my case the socket is located an /var/run/clamdclmilter.sock
I have added the following to the init.d script in the start section:
rm /var/run/clamd/clmilter.sock

Reproducible: Always
Steps to Reproduce:
1./etc/init.d/clamav-milter restart
2.check by either e-mail or by ps -A | grep milter
3.

Actual Results:  
The clamav plugin does not work and the e-mails are not checked.
Sendmail runs anyway and delivers unchecked e-mails
I had one virus entering my PC ( in this case a micisoft Xp ) but the local
virus scanner picked it up
There is no warning, one assumes to be save but is not!

Expected Results:  
remove the old socket and start!

Could the following also be added, maybe with a "#" to uncomment when needed:
in init.d
clamav-milter:
need antivirus
provide clamavmilter

clamd:
provide antivirus

sendmail:
need clamavmilter

This makes shure that everything is started in order!
Comment 1 Andrea Barisani (RETIRED) gentoo-dev 2005-06-02 23:56:46 UTC
clamav-0.85.1 is stable with new confd/init scripts.
Comment 2 Andrej Kacian (RETIRED) gentoo-dev 2005-06-03 01:42:27 UTC
Again, 0.85.1-r1 is the one with sendmail stuff. I'll mark it stable sometimes
tomorrow, I guess.
Comment 3 Andrej Kacian (RETIRED) gentoo-dev 2005-06-06 05:55:07 UTC
0.85.1-r1 stable on x86, this issue is fixed there.