Skip to content
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

handling crashed commands #1

Open
gggeek opened this issue Dec 21, 2017 · 1 comment
Open

handling crashed commands #1

gggeek opened this issue Dec 21, 2017 · 1 comment

Comments

@gggeek
Copy link
Contributor

gggeek commented Dec 21, 2017

If a command crashes, my gut feeling is that it will stay locked forever.
it would be nice to have an 'unlock' command to allow removing the locks.
Even better: to have a cronjob that automatically removes locks that are older than X days/hours

@bOnepain
Copy link
Contributor

bOnepain commented Jan 2, 2018

Isn't it the operating system that releases the lock (acquired by the flock function) automatically when the file is closed or the script crashes ? @gggeek Could you describe a use case where the lock was not properly released on script crash ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants