BTW, I think we should try to get the code that relies on
Storable out of SpamAssassin for 3.1.0. why?
Because as far as I can see we still have a lot of users reporting
problems with spamd hanging, and (last I heard) it looked like Storable
was the issue.
We've hacked around it with some alarm() timeouts, but we're not sure if
they'll work or not in all cases.
as far as I can see, we are possibly the biggest perl project using
Storable for such an essential and complex piece of code, and I think we
may be running up against the poorly-debugged edge case that nobody else
has had to deal with.
On top of that, I don't see exactly *why* Storable is required to
implement what it's doing (keeping a copy of the basic system-wide Conf
object's data). as far as I can see, we can do that a la
%{$conf->{tests}} = %{$basic_conf->{tests}}
ie. direct copying and assignment, in pretty much exactly the same
way we use Storable, but without the worries.
We have spamd reliability issues, I think, in the field -- and
cutting out one possible cause of that seems like a very good idea.
thoughts?
--j.
