http://bugzilla.spamassassin.org/show_bug.cgi?id=3828
------- Additional Comments From [EMAIL PROTECTED] 2004-11-24 06:47 ------- justin okay, but we still run into a similar deal here. the alarm that encompasses check() in spamd is what we would want to store as $oldalarm. and in order to restore $oldalarm we would have to get it passed into PerMsgStatus, since $oldalarm would be set per-child, per-check. 'actually, no, it's fine to do that -- each M:SA object is single-threaded.' but the spamd daemon only creates one instance of M::SA->new(), so storing start_time or $oldalarm or anything would not be child (per-check) specific, since M::SA->new() is not called per accept_a_conn(). or maybe i'm missing something here? The only things i see called per-check is M::SA::Message->new() and M::SA::PerMsgStatus->new(), so start_time or $oldalarm would need to be passed in there somehow to have access to it. or i guess instead of alarming spamd with timeout_child, it could be moved down to M::SA::check() instead. This would help people that dont use spamd take advantage of running command line spamassassin with a --timeout-child also. d d ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
