in reply to monitor process

If you are talking about checking a process on a "remote" server from some sort of "local" machine, and if you can run a login shell on the server (esp. if you can do "ssh that.server" from your local machine), and if both machines are *n*x or have gnu tools on them (lots of "ifs" there -- the OP leaves a lot to the imagination), then you could do something like: 
ssh that.server ps -flags | grep that_process

[download]
Note that you'll need to be careful about choosing the "ps" option flags -- seems like no two flavors of *n*x use the same option definitions for "ps" these days. Just run "man ps" on that.server and read the output.

Replies are listed 'Best First'.
Re^2: monitor process
by Bloodnok (Vicar) on Apr 24, 2009 at 11:38 UTC
    Hmmm ,

    That's all very well, graff, but it can only identify the situation whereby the remote server process has stopped running.

    I'm guessing, since the OP hasn't (yet) responded to a couple of requests for further information, that the OP has encountered the situation whereby the process appears to be running but is no longer responding to connection requests...hence either the heartbeat or polled approach (as mentioned elsewhere) would be the logical solution.

    A user level that continues to overstate my experience :-))
[reply]

In Section Seekers of Perl Wisdom