On 10:50 am, gand...@shopzeus.com wrote:
Suppose we have a program that writes its process id into a pid file.
Usually the program deletes the pid file when it exists... But in
some cases (for example, killed with kill -9 or TerminateProcess) pid
file is left there. I would like to know if a
Suppose we have a program that writes its process id into a pid file.
Usually the program deletes the pid file when it exists... But in some
cases (for example, killed with kill -9 or TerminateProcess) pid file is
left there. I would like to know if a process (given with its process
id) is st
On Tue, 29 Dec 2009 12:35:11 +0430, Laszlo Nagy wrote:
> Suppose we have a program that writes its process id into a pid file.
> Usually the program deletes the pid file when it exists... But in some
> cases (for example, killed with kill -9 or TerminateProcess) pid file is
> left there. I woul
Hi!
For Windows, you can use the command-line tasklist
Example:
tasklist
tasklist /FI "IMAGENAME eq iexplore.exe"
tasklist /FI "PID eq 4044" /FO LIST
The last line is for known PID. Prior for search by (exe's) name.
Note than STATUS give if the process is RUNNING / NOT RESPONDING / etc
Am Tue, 29 Dec 2009 12:35:11 +0430 schrieb Laszlo Nagy:
> Suppose we have a program that writes its process id into a pid file.
> Usually the program deletes the pid file when it exists... But in some
> cases (for example, killed with kill -9 or TerminateProcess) pid file is
> left there. I would l
Suppose we have a program that writes its process id into a pid file.
Usually the program deletes the pid file when it exists... But in some
cases (for example, killed with kill -9 or TerminateProcess) pid file is
left there. I would like to know if a process (given with its process
id) is stil
