http://bugzilla.spamassassin.org/show_bug.cgi?id=3828
------- Additional Comments From [EMAIL PROTECTED] 2004-11-23 15:01 -------
okay, help me understand the flow here in spamd, this is what i see..
1) spamd M::SA->new
2) spamd spawn children
3) spamd accept_a_conn()
4) spamd check()
5) M::SA::parse() (new Message)
6) M::SA::check() (new PerMsgStatus)
7) M::SA::PMS::check()
8) do all the tests
so, the optimal place to put a runtime calculator would be where? start_time on
that particular scan needs to be passed to either Message.pm or PerMsgStatus.pm
for storage to refer to it before the PMS::check() is ran. it cant be stored
in $self->{main} unless it was something like
$self->{main}->{pid_of_child}->{start_time} and let that child update the
start_time everytime it starts a new message. However, i think it would be
better if it were stored lower, in something that was destroyed after the check
was complete.
all placement considerations aside, do you think this is a reasonalbe idea to
set the alarm time back to "timeout_child - runtime" instead of zeroing it out?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
