Re: Testing if your code successfully flocked

Works for me in FreeBSD and Windows:

use strict;
use warnings;

use Fcntl ':flock';

open my $fh1, '>>', 'moo'
or die "Cannot open moo for appending (1): $!\n";

print(flock($fh1, LOCK_EX | LOCK_NB) ? 1 :0, "\n");

open my $fh2, '>>', 'moo'
or die "Cannot open moo for appending (2): $!\n";

print(flock($fh2, LOCK_EX | LOCK_NB) ? 1 :0, "\n");
[download]

1
0
[download]

Comment on Re: Testing if your code successfully flocked Select or Download Code

Replies are listed 'Best First'.
Re^2: Testing if your code successfully flocked by dragonchild (Archbishop) on Apr 26, 2005 at 15:07 UTC
On Solaris, I get: `$ perl a 1 1` [download] I think Joost is right, which sucks rocks. sighs The Perfect is the Enemy of the Good.	[reply] [d/l]
Re^3: Testing if your code successfully flocked by Joost (Canon) on Apr 26, 2005 at 15:13 UTC
For a work-around, I guess unlocking the file in the child process, and then re-issuing the flock() /should/ work, but to be 100% certain, close() and re-open the file in the child process. Update: Interestingly, on linux the above code outputs `1 0` [download] So there the lock seems to be associated with the handle, not the file. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply] [d/l]