https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5950
--- Comment #5 from Tom Vajzovic <[EMAIL PROTECTED]> 2008-08-04 13:05:21 PST --- You are quite right that I am being a little closed-minded in thinking that this is all about the pid file. The pidfile is only part of the issue. What I would like is that the process I start doesn't disconnect from the terminal until the daemon is ready to accept connections, too. In daemonize() we have: exit if $pid; what I would like is that this does: if($pid) wait until daemon is ready to receive connections, AND has written its pidfile if requested, then exit. Perhaps my requirements are quite different from the usual situation where spamd is started at boot and it is best to be fast and to disconnect ASAP. If that is the case, would an alternative option --daemonize-when-ready be acceptable to help me in this case? I am happy if the answer is "No, you have to read the log", but rather than having shell scripts try to make sense of the log, wouldn't it be better to keep this internal to SA? I'd rather not have to check if the log format has changed in every new version. Thanks for your time, viza -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
