On Tue, May 20, 2008 at 10:10:02AM -0400, Noah Meyerhans wrote: > On Tue, May 20, 2008 at 06:20:33AM -0700, Daniel Burrows wrote: > > A much larger amount of spam than usual got through my filters, I > > think because most of my spam checks couldn't run due to this error. > > After some confusion, I figured out that I had upgraded perl under a > > running spamd, from 5.8 to 5.10. Apparently spamd needs to dynamically > > load perl modules, and removing the 5.8 versions breaks it. It would be > > great if spamd could be restarted when perl is upgraded. I suspect this > > is not exactly trivial, which is why I'm filing at wishlist severity.
Would it be possible to keep the 5.8 module tree around, for running processes to dynload? It's very common for long-running perl processes to need to load a new module at runtime, long after the process was started; SpamAssassin won't be the only one. > There are a few different things that need to happen to spamassassin > when perl is upgraded. Compiled rules need to be blown away and > rebuilt, for example. Regarding this -- bug #479865 -- that's a separate issue, and simply a bug in SpamAssassin. There's no need to hack the perl package to deal with it. It will be fixed upstream (once I can get the votes on https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5899 and a 3.2.5 release put out... ;) --j. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
