Fix permissions of mutex files #741
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Raised in #736
Description
Previous code had these two lines, which were removed in the new locking code, since I though they're not needed anymore. Looks like you have to clear this umask which is applied to all files being created in order for the maske 666 to be respected
List of the changes
Testing
I've manually run tests which create locks, and observed prior to the change:
-rw-r--r-- 1 brosko group_1211400513 48 Apr 14 11:26 TT_UMD_LOCK.CREATE_ETH_MAP
after the change:
-rw-rw-rw- 1 brosko group_1211400513 48 Apr 14 14:04 TT_UMD_LOCK.CREATE_ETH_MAP
API Changes
There are no API changes in this PR.