On Mon, 7 Mar 2005, Theo Van Dinter wrote:
On Mon, Mar 07, 2005 at 09:25:48PM -0500, Dan Mahoney, System Admin wrote:what message a child is chewing on. No clear indication of where such a message would be stored, or some way to just send a spamd child a sigusr2 and have it return the message unprocessed.
Sure there is. Just kill the child. spamc will eventually return the message unprocessed.
Actually, my experience has been that the child in this case doesn't respond to kill -TERM, even after larger delays like five minutes with repeated kill'ing. Kill -9 seems to cause another process to pop up with similar (instant) loads. Nuking the users' bayes/awl databases does not seem to fix the problem.
Alternately, if you know the spamd process, you can figure out which spamc process is calling pretty easily (lsof/etc) and can just kill that instead. If you're using procmail, it'll just send the message through unmodified.
-- Randomly Generated Tagline: All intelligent species own cats.
--
"It's buttery kettle ASS corn!"
-Dan Mahoney, Ezzi Computers, 10/22/03, 2AM
--------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---------------------------
