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
If for some reason the key file for a lock is missing, there is no way to get out of this situation just using mq.sh.
mq.sh
It should be safe to just rm the corresponding lock file, but we don't want users to have to do that manually.
rm
The situation should be extremely rare, but it is not entirely impossible, so at least info and signal should deal with it gracefully.
info
signal
The text was updated successfully, but these errors were encountered:
mq.sh sem -signal -f foo should work even if the key file is missing.
mq.sh sem -signal -f foo
Sorry, something went wrong.
I think that didn't work for me last time I tried it.
lsf37
No branches or pull requests
If for some reason the key file for a lock is missing, there is no way to get out of this situation just using
mq.sh
.It should be safe to just
rm
the corresponding lock file, but we don't want users to have to do that manually.The situation should be extremely rare, but it is not entirely impossible, so at least
info
andsignal
should deal with it gracefully.The text was updated successfully, but these errors were encountered: