-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flock/fcntl bug in perl V5.005_03 #506
Comments
From dorfmann@kesoftware.comCreated by dorfmann@kesoftware.comflock() and/or fcntl() do not appear to work correctly in perl5.005_03 under Solaris 2.5 PLEASE NOTE: I've included the "perl -V" configuration info for the solaris and linux The problem is that flock *always* reports that the lock is granted. If you run two instances Please note that I tried a pre-built binary release of perl5.005_03 on solaris File locking with "flock()": ############################################################################## ############################################################################## File locking with "fcntl()": ############################################################################## my $flock_struct = pack("sslll", F_WRLCK,0,0,0,0); ############################################################################## Perl Info
|
From [Unknown Contact. See original ticket]William Dorfmann wrote:
The bug is actually in your program. Your subroutine which opens and locks a To fix your program, you could either move your 'lock' subroutine definition to sub lock; # Full definition further down If in your actual program (rather than this test case) your lock subroutine is Note that there's no 'unlock' reserved word, so you don't have to predeclare
-- |
Migrated from rt.perl.org#1352 (status was 'resolved')
Searchable as RT1352$
The text was updated successfully, but these errors were encountered: