I had a customer e-mail me today saying that their mail system had stopped
processing mail last night, finding that amavisd had stopped.  Larry sent
me an excerpt from the amavisd log that indicated that the TCP process
couldn't bind because the port was already in use.

This sounded like a problem that might occur when a process is restarted
using rc run control, and looking at the rc.amavisd script, sure enough it
does a restart during log processing.

There is a two second sleep in the %restart section of the rc.amavisd run
control script.  I think it might be a good idea to bump this
significantly, say to 20 seconds or so.

This would explain several occassions where our main mailing list server
here stopped working with a dead amavisd process.  That machine isn't
particularly fast, and the load average can get pretty high when delivering
large Mailman lists.

I think this also is applicable to apache as I've seen many instances where
it takes longer than the 2 second sleep time in the apache %stop section
before all the apache processes are complete.

Bill
--
INTERNET:   [EMAIL PROTECTED]  Bill Campbell; Celestial Software LLC
UUCP:               camco!bill  PO Box 820; 6641 E. Mercer Way
FAX:            (206) 232-9186  Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/

``My reading of history convinces me that most bad government results
from too much government.'' --Thomas Jefferson.
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

Reply via email to