Actually after some more investigation, I found out that clamd seems to hang (at least in some Linux installations), if in startup the stderr and stdout streams stop existing, which happens if it is started like this:
/usr/local/sbin/clamd /usr/local/sbin/clamav-milter -lo local:/var/run/clmilter.sock if, instead it is started with: /usr/local/sbin/clamd >/dev/null 2>&1 /usr/local/sbin/clamav-milter -lo local:/var/run/clmilter.sock >/dev/null 2>&1 it does not hang, when the /(root) user logs out from the system. Is this something which is properly documented, or have I just missed the documentation somewhere? yours, Tommi Rintala > > > Sep 19 08:14:01 mega sm-mta[25878]: h8J5A1BD025878: Milter (clmilter): to > error state > Sep 19 08:14:01 mega sm-mta[25878]: h8J5A1BD025878: Milter (clmilter): > timeout before data read > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
