Please include errno when raising LockError
Bug #1071766 reported by
nutjob
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zc.lockfile |
New
|
Undecided
|
Unassigned |
Bug Description
I've been getting intermittent startup errors on a Zope instance from zc.lockfile 1.0.0, zc/lockfile/
Unfortunately, there's no further information, as the try block catches the IOError and raises a fresh LockError.
That IOError does have a useful bit of data, though: the errno value left by the failed call to fcntl. With that, I'd have a clue as to what the underlying issue is.
Perhaps the errno could be included in the raised LockError's message, as suggested by the patch.
Thanks,
Sean "nutjob" Kelly.
To post a comment you must log in.