Regarding the part of your comment regarding PIDs, I believe you can kill 0, $pid to determine if a signal can be sent to that PID. If so, then verify that the PID is for a process executing the same script/program (by parsing the result of a 'ps' command, or using a module such as Proc::ProcessTable). 

# Untested
use Proc::ProcessTable;

my $tobj = new Proc::ProcessTable;
my $proctable = $tobj->table();
my $pid = 0;
for ( @$proctable ) {
    if ( $_->cmndline =~ m/$script_name/ ) {
        $pid = $_->pid;
        last;
    }
}
print $script_name, 
  ( kill 0, $pid ? q{appears} : q{does not appear} ), 
  q{ to be running}, qq{\n};

[download]

Hope that helps.

In reply to Re: reliable lockfiles? by atcroft
in thread reliable lockfiles? by temporal

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.