I'm writing a module that using flock() as part of its filehandling. (I'm on Solaris, if it makes any difference.) Like a good Perlmonkey, I'm writing a test, seeing it fail, writing some code, seeing it pass. Except, I'm running into a problem. (Assume the variables are all declared and set appropriately.)
001_sometest.t
--------------
use_ok( $CLASS );
my $obj = $CLASS->new(
filename => $logfile,
);
isa_ok( $obj, $CLASS );
ok( -e $logfile, "$CLASS created logfile" );
open my $fh, '>>', $logfile
or die "Cannot open '$logfile' for appending: $!\n";
my $rc = flock( $fh, LOCK_EX | LOCK_NB );
ok( !$rc, "Cannot flock $logfile" );
The point is that new() will open $filename for appending, then flock it with LOCK_EX. All this is happening successfully. Except, I don't seem to be able to test that I got the flock correctly. Is this because I'm trying to test a process-level lock within the same process? How would you test it? I don't want to whip out Proc::Background . . .
The Perfect is the Enemy of the Good.
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.