This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: KillAll SpamAssassin Processes
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: Herb Martin <HerbM at learnquick dot com>
- Cc: cygwin at cygwin dot com
- Date: Tue, 21 Mar 2006 17:03:40 -0500 (EST)
- Subject: Re: KillAll SpamAssassin Processes
- References: <EIWHVRC-000ILW-E4@mail2.learnquick.com>
- Reply-to: cygwin at cygwin dot com
On Tue, 21 Mar 2006, Herb Martin wrote:
> This should be simple but I haven't found the
> magic encantation so far:
>
> I wish to kill SpamAssassin and all child processes
> it has started.
>
> [My experience is that trying to signal -s HUP does
> not work with SA (on CygWin) but puts SA into some
> sort of unresponsive state.]
>
> I have other (than SA) Perl processes running so
> using "killall" with just the process NAME is not
> a good choice.
>
> So far no combinations of "killall" switches,
> e.g., using Group ID etc, have worked.
>
> My only useful method (other than hitting each process
> individually) has been to use -i (interactive) and then
> respond to each confirmation.
>
> Thanks for straightening me out -- I am sure this is
> very easy but haven't gotten it right yet.
You could put all the processes into their own process group (using
newpgrp() in perl, or bash's job control), and then doing a "kill -SIG
-PGID" to kill all processes in the group PGID.
FWIW, this is not Cygwin-specific.
HTH,
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/