Along the same lines as merlyn's suggestion; replace the 
system("/bin/rm $lock_file");

[download]
with 
unlink($lock_file);

[download]
Again you're saving launching another process.

One algorithmic problem with your lockfile approach is that if your process dies (for whatever reason) without removing the lockfile all subsequent runs of the program will think there's already an instance running; even though there isn't.

one last thing.... use strict. Learn what it is and start using it. It will save you much pain as you continue to learn and use perl.

In reply to Re: lock files vs. non-predictable file names by lhoward
in thread lock files vs. non-predictable file names by RuphSkunk

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.