Perl's signal handling is unreliable. I do not believe
that you need to catch signals or do any cleanup. My
understanding is that the OS is responsible for
flock.
If your process is terminated unexpectedly, the OS is
responsible for noting that your filehandles are now closed
and your locks are ended.
If anyone has any documentation to the contrary, please show
me. Also a failure script would be of interest. I am
currently relying on this behaviour in production and if it
is unreliable, I would really like to know. In the
meantime you can take the low-tech approach and run the
following script from multiple xterms while trying to
create a problem...
use Fcntl qw(:flock);
my $file = "my.lock";
open(FOO, ">> $file") or die "Cannot write to $file: $!";
print "Getting the lock\n";
flock (FOO, LOCK_EX) or die "Cannot flock $file: $!";
print "Locked by $$, hit enter to exit: ";
<STDIN>;
At least on Linux I am unable to get this to act in anything
other than the expected manner...
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.