Cruisecontrolrb users - Sep 2007 - Best way to stop all CC processes

Hi Folks.

Is there a slick way to kill all CC related processes? The best I''ve  
got so far is

ps aux |grep cruise

And then manually killing them.

Thanks,
John

On Sep 24, 2007, at 1:08 PM, John Bachir wrote:
> The best I''ve got so far is
>
> ps aux |grep cruise
>
Seems like a separate

ps aux |grep 3333

is also necessary.

On Monday 24 September 2007, John Bachir wrote:
> On Sep 24, 2007, at 1:08 PM, John Bachir wrote:
> > The best I''ve got so far is
> >
> > ps aux |grep cruise
>
> Seems like a separate
>
> ps aux |grep 3333
>
> is also necessary.

Really cool would be to have a "Kill this build job"-button per
project
(optional of course) in the webinterface.

Has anybody implemented such a thing yet?


Ciao,
   Daniel

-- 
J. Daniel Schmidt <jdsn at suse.de>         SUSE Linux Products GmbH 
Research & Development                   Maxfeldstr. 5
GF: Markus Rex, HRB 16746 (AG N?rnberg)  D-90409 N?rnberg

On 12/5/07, J. Daniel Schmidt <jdsn at suse.de>
wrote:
> On Monday 24 September 2007, John Bachir wrote:
> > On Sep 24, 2007, at 1:08 PM, John Bachir wrote:
> > > The best I''ve got so far is
> > >
> > > ps aux |grep cruise
> >
> > Seems like a separate
> >
> > ps aux |grep 3333
> >
> > is also necessary.
>
>
> Really cool would be to have a "Kill this build job"-button per
project
> (optional of course) in the webinterface.
>
> Has anybody implemented such a thing yet?
>
We had this functionality in the ''stop'' option of our init
script for
cruise.java.  It just uses the unix process info to walk a process
tree and kill everything.  It would be nice to have in cruise, but it
would be unix-only, and maybe distro-dependent.

Child processes are notoriously hard to manage in ruby, especially
across platforms.