While it would be nice to have a simple command that gives you the information you want, I disagree that parsing the output of ps is 'unportable'. It is certainly far more portable than /proc. The POSIX(ie SYSV) options for ps have been standardized for quite some time, as have the BSD options. Most systems I have worked with (AIX, Solaris, Linux, HP-UX) support the POSIX options. The only one that would require different syntax is FreeBSD.
You might try just keeping track of PID and procname between calls to your monitor. Using 'ps -ex | grep 'name1|name2|...' should give you what you want with either a POSIX or BSD ps(pid will always be first field). If the same PID/procname shows up twice in a row, kill it off. Just a thought...
fnord
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
