Allow group access to lockfile and fix growing or empty timestamp #1213
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
This allows the lockfile to be shared with users in the same group.
The group write flag allows sharing the lock with other users while removing the append flag prevents the lockfile growing if it is checked repeatedly over time.
This prevents the content being overwritten if the file is locked.
timopollmeier
changed the title
timopollmeier
changed the title
Using read mode does not work if the file does not exist.
mattmundell
approved these changes
Aug 3, 2020
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.
This allows gvmd and ospd-openvas to be run as different users in the same group and stops the timestamp in the lockfile from growing or being cleared when it is already locked.
Checklist: