Excellent approach and very standard. I would also think that the poster would want to install a signal
handler(s) to release appropriate locks if the program dies, get's a
CTL-C or whatever. Something like this:
$SIG{'INT'} = \&release_lock;
$SIG{'QUIT'} = \&release_lock;
$SIG{'PIPE'} = \&release_lock; #maybe too?
sub release_lock{
#...do what you can here...
}
The basic idea is not to leave locks around if your program abends. The
lock strategy is simple, works well, and can be implemented in many languages
on many O/s'es (some easier than others)..just remember to clean up if "bad things"
happen to your program and the normal "release lock" code doesn't execute.
The lock system is cooperative, meaning that everybody has to know what is
going on and cooperate. It is possible to write a file that is "locked" for
exclusive access. A file lock is more like an advisory thing and the programs
that use it have to "play by the rules".
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.