Avoid permission issues for the crash uploader script#6697
Merged
Conversation
richardstartin
approved these changes
Feb 19, 2024
This file contains hidden or 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
3 participants
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.
What Does This Do
For the crash tracking it adjusts the folder and file permissions such that they are not restricted to a single user/group.
Motivation
The crash tracking script initialization routine is creating the script on the fly. By default the defined folder and the script itself will be accessing only to the user/group that created them. This is causing issues on mutli-user systems where the script and the directory hierarchy may be created by one user and then used by another one.
Additional Notes
Jira ticket: PROF-9159