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

Exposing lock age #62

Open
josegonzalez opened this issue Nov 28, 2022 · 2 comments
Open

Exposing lock age #62

josegonzalez opened this issue Nov 28, 2022 · 2 comments

Comments

@josegonzalez
Copy link

I'm not sure if this is possible, but I'd be happy to try and help implement it if it's feasible.

My use case is in dokku, where we use this to ensure there aren't concurrent mutations of the docker state by ps:retire (since the command happens in the background). I'd like to be able to somehow detect that the lock is ancient and then delete the lock in that case (or at least exit with a different exit code). Right now, we don't have a file handle exposed via api that I could use to detect this and I'm looking for the "correct" way to do it if it is at all possible.

@ldez
Copy link
Contributor

ldez commented Jun 30, 2024

In a way, it's related to #56, but your request may be easier to add.
Maybe we can expose the Stat information 🤔

@josegonzalez
Copy link
Author

Yeah that seems maybe like a good alternative.

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

No branches or pull requests

2 participants