Yes, you do. You summarized the problem in killing off the
processes well, also.
I'm thinking the solution is in a compiled program, not a script,
that will get the process listing and kill off processes owned
by the offender. It seems shell scripts are too slow. Maybe
we could renice all the corewar to -20, give our hunter/killer
a +20, and let it go. Ideas???
George
"John (EBo) David" wrote:
>
> Nathan England wrote:
> >
> > >
> > > *** DO NOT TRY THIS UNLESS YOU WANT TO REBOOT ***
> > > Here's my script:
> > > #!/bin/bash
> > >
> > > while [ 1 ]; do
> > > # Make a copy
> > > cp corewar corewar.$$
> > >
> > > # Run it
> > > ./corewar.$$ &
> > >
> > > # Start over
> > > done
> > >
> > > *** DO NOT TRY THIS UNLESS YOU WANT TO REBOOT ***
> > >
> > > Here's the challenge: how do you clean up these processes without
> > > using init 0, init 1, init 6, reboot, or shutdown?
> > >
> > > Now I'm guilty of #3, above.
> > >
> > > George
> > >
> >
> > Use one of the bootable business cards. Boot that, mount your drive,
> > remove the script, reboot..
> >
> > yeah? or did I miss the point?
>
> This is what I understood the question to be:
>
> How does one kill *all* them processes without rebooting the machine.
>
> Well, if I *know* the name of the program causing the evil behaviour
> then I can write a awk/perl/sh script that parses the info from a 'ps'
> and then kills them all in turn. This could also be done
> recersively... The problem though is that the creation loop is likely
> faster then the seek-and-destroy-process loop. So that would not likely
> work either unless you nice your kill process to something like a -19.
>
> Do I understand the problem correctly?
>
> EBo --
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
>
> PLUG-discuss mailing list - PLUG-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)