Hi, I'm currently getting the message "Waiting for the process XXXXX to terminate" upon issueing an 'amavisd stop' command. Unfortunately, it waits forever until it gets kill -9'ed.
What changed? The libc in the amavis chroot got exchanged (while amavis was running), but since amavis launches from outside the chroot, this shouldn't affect amavis (or does it?). I tried lsof -p XXXXX (the master process) on the process, but nothing unsual was to be seen. The process itself was sleeping through it all. Unfortunately, this only happens on some machines, others are happily churning away and stopping after the exact same change took place. Mark, can you add a 30 (or 300) second timeout that will do a hard kill and bailout in that for(;;) loop? Regs, Sven ------------------------------------------------------ BAGHUS GmbH EDV und Internetdienstleistungen Staffelseestr. 2 81477 München Tel.: 0 89 / 8 71 81 - 4 84 Fax.: 0 89 / 8 71 81 - 4 88 www.baghus.net, [EMAIL PROTECTED] HRB: 144283, USt-IdNr: DE224865405 Junkmail Catcher, do not use: [EMAIL PROTECTED] ------------------------------------------------------ ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
