Always re-read your code [Was: Finding if a process is runing.]

AIL PROTECTED]> To: "Oded Arbel" <[EMAIL PROTECTED]> Cc: "Linux-IL Mailing list" <[EMAIL PROTECTED]> Sent: Thursday, February 08, 2001 10:37 Subject: Re: Finding if a process is runing. > check the kill(2) manual for the error codes returned by the kill() s

Re: Finding if a process is runing.

Oded Arbel <[EMAIL PROTECTED]> writes: > I'vre read somewhere (I think in one of perl's man pages) that you can use > kill to send a "0 signal" to a process, to see if it is still > runing. POSIX says so, AFAIK. > kill(2) man page seems to confirm that, saying that if sig is 0, no signal > wil

Re: Finding if a process is runing.

On Thu, Feb 08, 2001, Oded Arbel wrote about "Finding if a process is runing.": > I'vre read somewhere (I think in one of perl's man pages) that you can use > kill to send a "0 signal" to a process, to see if it is still runing. the > kill(2) man page seems

Finding if a process is runing.

Hi list. I'vre read somewhere (I think in one of perl's man pages) that you can use kill to send a "0 signal" to a process, to see if it is still runing. the kill(2) man page seems to confirm that, saying that if sig is 0, no signal will be sent, but error checking is till performed - from which