We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
The text was updated successfully, but these errors were encountered:
Allow specifying the lockfile path directly
ac6aa0e
This closes #48, by allowing the user to specify a lockfile explicitly - rather than relying upon the automatic construction.
skx
Successfully merging a pull request may close this issue.
sometimes multiple different commands might compete of one lock, in that case it is necessary to have a well-known lock-file.
in the example above cmd1 and cmd2 are sharing lock-group1 and cmd3 and cmd4 are sharing lock-group2
The text was updated successfully, but these errors were encountered: