When two secbox instances are using --nfs the first which terminate umount the exports #2
Comments
StayPirate
added a commit
that referenced
this issue
Apr 1, 2021
This is a partial fix for #2, only fixes the current implemented nfs option. A similar check for sshfs will need to be added once sshfs is supported.
StayPirate
added a commit
that referenced
this issue
Apr 5, 2021
Add sshfs support. This also solve #2.
|
solved with #4 |
StayPirate
added a commit
that referenced
this issue
Apr 9, 2021
This is a partial fix for #2, only fixes the current implemented nfs option. A similar check for sshfs will need to be added once sshfs is supported.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I run
secboxtwice at the same time with the flag--nfs(same would happen with--sshfs#1) after the faster process terminates, secbox then umount the NFS exports leaving the second secbox instance without the needed resources.Need to add a check before release the resources... check if another secbox instance are using them.
The text was updated successfully, but these errors were encountered: