Re: Killing a process that doesn't exist!?

[Reid Priedhorsky <reid@reidster.net>]

On Fri, 12 Jan 2007 15:00:26 +0100, Glen Yu wrote:

> Hi everyone,
> 
> I have a script that I normally run (called "extract.sh") but can't seem to
> run it today because everytime I run it, it says that it's already running
> :| , but if I do "ps -ef | grep extract", nothing shows up.  The log file,
> however, tells a different story:
> 
> Fri Jan 12 08:03:01 EST 2007, >>>>>>>>>>>>>>>>>>>> extract.sh is already
> running, pid: 29669
> Fri Jan 12 08:05:29 EST 2007, >>>>>>>>>>>>>>>>>>>> extract.sh is already
> running, pid: 270
> Fri Jan 12 08:05:53 EST 2007, >>>>>>>>>>>>>>>>>>>> extract.sh is already
> running, pid: 277
> Fri Jan 12 08:08:09 EST 2007, >>>>>>>>>>>>>>>>>>>> extract.sh is already
> running, pid: 1054
> Fri Jan 12 08:16:41 EST 2007, >>>>>>>>>>>>>>>>>>>> extract.sh is already
> running, pid: 2154

I've run into this sort of thing before and it turned out to be tripping
over the grep process. Does your script also 'ps -ef | grep extract'
or something similar? If so, the PIDs might be those of the grep process.

Good luck,

Reid