El Lun 29 Sep 2008, escribiste: > Hello, > > sorry for the late answer, I didn't had the time to work an the > package lately... > > Fernando J. Rodríguez <[EMAIL PROTECTED]> writes: > > I discovered that if I issue the /etc/init.d/mailscanner stop > > command while MailScanner is still autodetecting virus scanners > > (calling in turn the helper scripts in > > /etc/MailScanner/wrappers), it correctly kills 3 running > > instances of MailScanner and no other one is spawned. But if I > > wait until the autodetection ends, the script kills the 2 running > > instances, but a new one is spawned as I showed in my first > > message, a new instance that start-stop-daemon does not kill (I > > think it does not send any signal to that process), but still > > keeps waiting for it to finish (which never happens, because there > > is no reason for it). > > > > If I supress the autodetection of available virus scanners, by > > putting the name of one of them (f-prot in my case) instead of > > "auto", and I run: /etc/init.d/mailscanner start; sleep 5; > > /etc/init.d/mailscanner stop the bug happens. > > On the other hand, > > /etc/init.d/mailscanner start; 5; /etc/init.d/mailscanner stop > > does not cause the bug to happen. > > > > So there is some time window between starting and stopping > > MailScanner where the bug occurs. > > > > Does any of this make any sense to you? > > Some, yes ;) > > Could you replace line 129 in the init.d script with > > start-stop-daemon --stop --retry=TERM/10/TERM/20 --name $NAME > > and try again?
That seems to address the issue! For example, if I add --verbose to the invocation of start-stop-daemon in line 129 I get this output: Stopped MailScanner (pid 26897 26898). Stopped MailScanner (pid 26974), retry #1. Good thing you managed to understand the explanation and implications the schedule in --retry in the start-stop-daemon man page... I coudn't, but now it's so obvious. :-) Now I wonder what would happen if I had 2 virus scanners installed: will 2 rogue processes be spawned instead of just 1, requiring a third TERM signal in the schedule? So I installed clamav and made sure it was detected by MailScanner: the schedule TERM/10/TERM/20 was still sufficient to properly end MailScanner. This bug is fixed for me. Thank you! -- Herr Groucho ID Jabber: [EMAIL PROTECTED] Clave pública GPG: hkp://pks.lugmen.org.ar Fingerprint GPG: B7BD 0FC7 D9A2 66F3 4EFC 45EE 7DE2 3932 597B 6354 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
