>The init script uses 'retry' for 30 seconds to kill the processes. If >they don't die on the first signal, they get signalled again, and so on >until they actually do die. This had to be done because I had seen >several heavily loaded systems where the milter processes wouldn't >actually die. The error message is obnoxious, but so far harmless. Do >you actually see any milter processes left after the init script exits?
I don't believe that there are any milter processes after the init script exits. I have written init scripts in the past for slackware and found that you need to pause before reloading the milter after doing a "killall" (usually about 3 seconds is OK) - I guess what you describe is a similar thing. Maybe I'll just revert back to the default init script - it sounds safer (even if it is a bit ugly). Its much less likely to break when I upgrade the clamav package. My mail server is only going to be for a small office - I don't think that "heavily loaded" applies here. Would it be feasible to change the 30-second timeout, or should I just leave well alone? ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
