Skip Menu |

This queue is for tickets about the Lazy-Lockfile CPAN distribution.

Report information
The Basics
Id: 121894
Status: resolved
Priority: 0/
Queue: Lazy-Lockfile

People
Owner: jeagle [...] cpan.org
Requestors: MRDVT [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 1.20
Fixed in: (no value)



Subject: Lazy::Lockfile failed to keep multiple process from starting when file system was full
Lazy::Lockfile appeared to not work when the file system became full. I believe that the process could not create a lock file and thus did not create a lock but somehow thought that it did create the lock file. I'm running perl-5.10.1-144.el6.x86_64 with perl-Lazy-Lockfile-1.20-1.el6.noarch as packaged by CentOS but there are no code changes between version 1.20 and 1.22. I use this constructor. my $lockfile = Lazy::Lockfile->new("/tmp/xxxx.lock"); if ($lockfile) { #process } else { #log failed lock } I have not tried to reproduce the issue at this time.
I've uploaded version 1.23 to CPAN which should fix this issue. 1.23 will check the return value of syswrite to determine if the PID was successfully written or not. I'm assuming that's where things fail when the filesystem is full so I believe this should resole the issue. Let me know if something breaks again.
On Tue May 30 01:37:33 2017, JEAGLE wrote: Show quoted text
> I've uploaded version 1.23 to CPAN which should fix this issue.
I have been using the updated version for years now and have never had this particular issue in the wild again. I'm going to mark this issue as resolved.