This post is actually in reply to both previous comments (merlyn's and graff's).

There is nothing quite like posting your code to an open forum to make you write better code...  :)    Thank you for your comments.

The o in m//o was something I pulled from Programming Perl, 3rd edition.  It is supposed to give a hint to the regexp compiler that the regexp only needs to be compiled once.  I suppose the same thing could be achieved with qr//.  Also, good catch on blindly using $1.

I can see how, in a general purpose setting, -9ing a process would be a Very Bad Thing.  This is the first thing on the bug list.  As for systeming out for kill instead of using the built-in, does the built-in allow you access to the error codes?  Also, because the code was already system dependent (ps -eaf), I figured why not add some more (sort of like using $& and friends in a regexp).  The world in which I work/play/code consists of Solaris, Irix, and Fedora Core 2.  So within my admittedly small world, the code works.

I will be updating the above code over the next day or two (as time permits) to fix your observations of what is wrong.  BTW, does anyone know where there is a list of all the strings $^O could contain?

In reply to Re^2: ppk by northwind
in thread ppk by northwind

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.