On Sat, 16 Feb 2002, Tom Lipkis wrote: > Modifying the site-wide config requires killing and restarting spamd, > which risks missing some mail or killing a running scan. It would be > handy if sending SIGHUP to the parent spamd process would cause it to > reload the rules cleanly. It should leave the listen up, and ideally it > would continue to accept connections but defer processing them until > it's done (else the listen() backlog might fill and new connections be > refused).
If you simply can't miss any mail, there is an easy workaround. Start a new spamd on a new port; Change the spamc config to point to that new port. Kill the old spamd. Start a new spamd on the normal port; Change spamc to point to the normal port. Kill the alternate-port spamd. Silly, but functional. -- Charlie Watts [EMAIL PROTECTED] Frontier Internet, Inc. http://www.frontier.net/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
