philipbailey,
We seem to be speaking past one another. At no point have I said the in-house developed script needs to know if itself is running. While the scripts my co-workers may write are in-house scripts, they will be interacting with the process table and any process that may be running there. One (of many) features I would like this library to have is the ability to answer questions like:

• Is /usr/bin/hello running (even if it may look like sh ../hello in the process table)
• Of the bazillion /usr/bin/java processes that are running, are any running with command line arguments that have the max heap space set to above 3GB

I assure you that I read your post carefully and I am sorry if I came across at not being appreciative of your response. Perhaps I am too close to the problem. To try and be clearer - the library is a general purpose way for in-house developed scripts to interact with the process table - even when those processes are not in-house.

---

---

• 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.