I read all the stuff about flock and its traps,and the biggest
one is always at the end, where it always sounds like
"Some versions of flock() can't lock files over a
network (e.g. on NFS file systems)" etc. I need to lock files
over NFS, so I read the stuff about fcntl, but it looked
rather complicated. I found a different solution in the manpage
open(2) in the section about O_EXCL. It goes like this:
sub lock {
my $lockhelper="lockhelper-$ENV{HOSTNAME}-$$.LCK";
my *LOCK;
my $nlink;
open(LOCK, ">$lockhelper") or die "Couldn't open() $lockhelper: $!";
+
print LOCK "$ENV{HOSTNAME};$$\n";
close(LOCK);
link($lockhelper, "lockfile.LCK");
(undef,undef,undef,$nlink,undef,undef,undef,undef,
undef,undef,undef,undef,undef) = stat($lockhelper);
unlink($lockhelper);
return $nlink==2;
}
If this sub returns true, you have got the lock, it is
nonblocking. My Question is: Is this really
the
way to do it if you have to deal with NFS, or is there a more
elegant way ?
- chb
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.