-
-
Notifications
You must be signed in to change notification settings - Fork 115
Best practice removal of lock file? #76
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
Comments
POSIX lockfiles are a little messy. Given the current state of locking mechanisms in *Nix systems (idk how any of this works in Windows and only superficial knowledge in linux), you probably want your application to control the state of the lock, based on your use-case.
https://stackoverflow.com/a/9464945/3988037 The safest is to have a separate One way (probably the best overall approach) would be to wrap your locking logic in a context manager at the application/stack level and remove the lock file on Better yet, use a This is already mentioned in the source And the answer is...it's again quite messy: |
Thanks -- yes, we have been noticing the messiness; it's even worse when you have multiple servers accessing NFS. |
Once the lock has been released, what is the best practice method for deleting the lock_file? Any chance of adding that to the docs.
Cheers!
The text was updated successfully, but these errors were encountered: