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

let with-lock specify the lockfile to use directly #48

Closed
terefang opened this issue May 27, 2023 · 0 comments · Fixed by #50
Closed

let with-lock specify the lockfile to use directly #48

terefang opened this issue May 27, 2023 · 0 comments · Fixed by #50
Assignees

Comments

@terefang
Copy link

terefang commented May 27, 2023

sometimes multiple different commands might compete of one lock, in that case it is necessary to have a well-known lock-file.

/path/to/sysbox with-lock -prefix /var/tmp/ -lockfile processing-lock-group1 /path/to/command1 [flags1]

/path/to/sysbox with-lock -prefix /var/tmp/ -lockfile processing-lock-group1 /path/to/command2 [flags2]

/path/to/sysbox with-lock -prefix /var/tmp/ -lockfile processing-lock-group2 /path/to/command3 [flags3]

/path/to/sysbox with-lock -prefix /var/tmp/ -lockfile processing-lock-group2 /path/to/command4 [flags4]

in the example above cmd1 and cmd2 are sharing lock-group1 and cmd3 and cmd4 are sharing lock-group2

skx added a commit that referenced this issue Jul 11, 2023
This closes #48, by allowing the user to specify a lockfile
explicitly - rather than relying upon the automatic construction.
@skx skx self-assigned this Jul 11, 2023
@skx skx closed this as completed in #50 Jul 12, 2023
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

Successfully merging a pull request may close this issue.

2 participants