Thomas Schulz wrote:
> In article <1169046937.102623.318180@51g2000cwl.googlegroups. com>,
> Tranz <mcass22135@hotmail.com> wrote:
> >
> >Dexthor wrote:
> >> > Dexthor, I did think of this and we have 100s, sometimes 1000s of
> >> > simulationous processes running, so narrowing it down could be
> >> > difficult. And if there was something running in the background
> >> > looking for patterns to kill. I would imagine it would kill the same
> >> > process everytime. Where as now it dies once and then upon restart it
> >> > is just fine.
> >> >
> >> > None of the processes run as root.
> >>
> >> For example: Suppose I am writing a smart watchdog script which reads a
> >> file or someother source for patterns a PID string or a process string.
> >> ps -ef |grep "pattern"|awk '{ print $2}'|xargs kill
> >>
> >> if the pattern above is a PID string, and suppose it is 162, it can
> >> match any PID which has pattern "162" in it. I think pgrep also
> >> suffers from similar shortfalls.
> >>
> >> If I were you, I will start with any processes that seem to be "shell
> >> scripts" which is where there is a good chance for mistakes.
> >>
> >> Can you sweep the server for all "shell scripts and see which ones try
> >> to do a kill" ?? Something to start with ?
> >>
> >> -Dexthor.
> >
> >Ahhh ok I understand what you are saying. Intresting. Ya I will scan
> >for kill.
> >
> >Odd thing is I have done some experments using the kill command. I have
> >never got stderr to print out "16113 Killed" It always says "Terminated"
> >
>
> If you do a 'kill -9' or a 'kill -KILL' you will get a 'Killed'.
> --
> Tom Schulz
> schulz@adi.com

I scanned all the production jobs, none have a kill command in them.
Now there still could be some that run as root. I am unable to view
those.

Also thanks about the kill -9, that does put Killed, but still can't
get it to say 16113 Killed.