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.

Sign up for GitHub

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

Jump to bottom

synchronize access to configfs #36

Open
agrover opened this issue Oct 25, 2013 · 1 comment
Open

synchronize access to configfs #36

agrover opened this issue Oct 25, 2013 · 1 comment

Comments

@agrover
Copy link
Contributor

agrover commented Oct 25, 2013

As raised on target-devel, it is possible that more than one agent could be changing configfs at the same time. This is very bad. We should establish a locking convention that all target configfs-accessing libs (not just this one) will follow in order to make configfs changes atomic.

Some kind of lockfile would be the normal way to do this, I guess.
@agrover
Copy link
Contributor Author

agrover commented Sep 20, 2017

see #91 and #42 for some attempts at solving this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@agrover