HOWEVER: I think this is a weak approach. As in for example a RedHat e +nvironment where the COLUMNS env is set to something smaller, all inf +o wouldn't be presented. ...
You can always use ps --cols NNN -elf | grep ... or set the COLUMNS environment variable before invoking ps.
Another option is to have each daemon open a Unix domain socket whose path is based on their id, e.g. daemon instance N opens /var/control/name_N. This can serve multiple purposes: 1) you can check to see if the daemon is running by trying to connect to the socket. If the daemon isn't accepting on the socket then you can asume it isn't running. 2) you can talk to the daemon via the socket and issue control messages or get a status, etc.
Update: Also with the socket approach, you can get the pid of the daemon that has the socket open by using lsof. This lets you hand off keeping track of this detail to the OS.
In reply to Re: Control other processes
by pc88mxer
in thread Control other processes
by Tronen
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |