On 14/02/2007 20:09, Rick Pim wrote:
it's true; if i start clamd and then check, the clamd socket isn't
there. but if i leave clamd alone for a few seconds the socket
appears and clamav-milter starts happily after that. i've tucked
a "sleep 30" into the startup script and things seem happy. is
there anything obvious i'm missing?
That will be because it forks before reading the database (which causes
the delay) and before creating the sockets. I.e. the initial process
exits before everything is ready.
Maybe it would be better if it forked after creating the sockets.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <[EMAIL PROTECTED]> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
