-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 16 Oct 2006 21:56:36 -0400, Daryl C. W. O'Shea wrote:
>Jo Rhett wrote: >> Daryl C. W. O'Shea wrote: >>> For now, running an sa-update, then a spamassassin --lint, and then >>> restarting is pretty safe though. >>> sa-update [whatever] && spamassassin --lint && whatever-to-restart >> >> I've been having some issues with the restarts, and when that happens >> mail is down. > >I'd say that's an issue of it's own, regardless of what sa-update does. > > >> I'm kindof hoping that there will be some way to get SA to re-read the >> rules *WITHOUT* restarting the process. > >You can SIGHUP the parent. It's nearly as heavy weight but should avoid >problems with the socket not being released in time for the new process >to get it -- which sometimes happen when stopping then starting it in a >rc script / whatever. Or you can check that spamassassin is running after restart and if not, start it again. Also you can check that there actually was an update before doing the restart in the first place. Works for me :-) Frank Bures, Dept. of Chemistry, University of Toronto, M5S 3H6 [EMAIL PROTECTED] http://www.chem.utoronto.ca PGP public key: http://pgp.mit.edu:11371/pks/lookup?op=index&search=Frank+Bures -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0 OS/2 for non-commercial use Comment: PGP 5.0 for OS/2 Charset: cp850 wj8DBQFFNMwzih0Xdz1+w+wRAtOnAKD6Rt+Q4Q/2af6T0jlt0mEjWsTEJACgs93b wHHnHTKAoN9X/AnQWSfx68Y= =5bgK -----END PGP SIGNATURE-----
