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

Replace hook execution fslock with mutex implementation. #5663

Merged

Conversation

howbazaar
Copy link
Contributor

@howbazaar howbazaar commented Jun 20, 2016

This work completely removes all use of fslock from the juju core codebase.

The uniter hook execution lock is now a named juju/mutex. The name is defined as a constant in the agent package, and passed to the workers that need it as manifold configuration for those that have manifolds, or as params to those that don't.

(Review request: http://reviews.vapour.ws/r/5107/)

This work completely removes all use of fslock from the juju core codebase.

The uniter hook execution lock is now a named juju/mutex. The name is defined as a constant in the agent package, and passed to the workers that need it as manifold configuration for those that have manifolds, or as params to those that don't.
@howbazaar howbazaar force-pushed the 1.25-replace-agent-machine-lock-with-mutex branch from d48788d to 8e9561d Compare June 20, 2016 19:57
@howbazaar
Copy link
Contributor Author

$$JFDI$$ can't find the 1.25 bug, but this causes real problems.

@jujubot
Copy link
Collaborator

jujubot commented Jun 20, 2016

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju

@jujubot jujubot merged commit 177c3dc into juju:1.25 Jun 20, 2016
@howbazaar howbazaar deleted the 1.25-replace-agent-machine-lock-with-mutex branch October 10, 2018 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants