>> I had an old path in there, and when traffic hit 35 processes, it would >> attempt to log a warning: >> >> write(2, "WARN: 35 active connections.\n", 29) = -1 EPIPE (Broken pipe) >> >> to the non existent (pipe?) and kill off the parent process. >> >> This is a bit of a subtle misconfiguration, and only debugable via strace >> when you are actually hitting the ceiling of your MAXDAEMONS=40. (Sam, don't >> tear my head off, but would it make any sense to refuse to start if that >> pipe is non-existent or not die if it can't be written to?) > > Why would I want to tear your head off? This is certainly something that > needs to be addressed >
Heh, because it was due to my own misconfiguration and this list can be a scary place to exhibit one's stupidity while requesting you to mollycoddle future attempts to replicate such actions. I've been using Courier for many many years now and really love it and the work you've done for us, so no disrespect was intended. J ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
