Subject: | "-warn" option doesn't work as documented |
Date: | Sat, 26 Apr 2008 17:48:26 +0200 |
To: | bug-LockFile-Simple [...] rt.cpan.org |
From: | gregor herrmann <gregoa [...] debian.org> |
Hi,
we've received the following bug report againt LockFile::Simple
(tracked as http://bugs.debian.org/478040 )
It looks like LockFile::Manager doesn't care about the "-warn"
attribute, which might or might not be intended but the POD in
Simple.pm suggests otherwise.
Thanks in advance for looking into this issue.
Cheers,
gregor (Debian Perl Group)
----- Forwarded message from Adrian von Bidder <avbidder@fortytwo.ch> -----
Subject: Bug#478040: liblockfile-simple-perl: "-warn" option doesn't work
Date: Sat, 26 Apr 2008 16:39:02 +0200
[..]
I'm calling LockFile like this:
LockFile::Simple->make(
-autoclean => 1,
-hold => 0,
-stale => 1,
-warn => 0)->lock('/var/lib/nihilist/db') || die "...";
so I can just forget about the lock and it will be removed for me when
the program is done. However, I get "WARNING: releasing 1 pending
lock..." at program exit. Setting -wfunc => undef instead of -warn
solves the problem, but warn is documented to suppress warnings too.
[..]
Show quoted text
----- End forwarded message -----
--
.''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4
: :' : debian gnu/linux user, admin & developer - http://www.debian.org/
`. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/
`- NP: Bob Dylan and Tom Petty: Knockin' On Heaven's Door
Message body not shown because it is not plain text.