So I wasn't the only one to see the Razor-related freeze-ups in spamd
tonight. I had 130 spamd's running on a server before I turned off the
MTA. After I brought things back under control, I decided figuring out
the problem could wait until tomorrow. I don't have the same version
of SpamAssassin running at home to look at now.
Has anyone found the bug? Razor checks are _supposed_ to
timeout. While all of this was happening, if you ran spamassassin, it
would properly timeout. If you fired up spamd, it would properly
timeout the Razor check during the initialization (watch the debug
output), but the children it spawned would all hang _forever_ in the
Razor check rather than timeout. That makes me suspicios that
something was not being reinitialized in the timeout check or some
other issue due to spamd being a bit of a kludge in the first place.
--
Crist J. Clark | [EMAIL PROTECTED]
| [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/ | [EMAIL PROTECTED]
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
