Set permissions on /opt/puppetlabs/pe_databases and /opt/puppetlabs/pe_databases/scripts #18
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
…ess /opt/puppetlabs/pe_databases/scripts because the mode becomes 0700 and is owned by root
instead of STDOUT
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.
When umask is restrictive (eg: 0077), the pe-postgres user cannot access /opt/puppetlabs/pe_databases/scripts because the mode becomes 0700 and is owned by root. This sets the mode to 0755 which allows pe-postgres to access the scripts.
I also fixed a minor logging issue in the backup script. It was putting the truncate command output to stdout instead of into the log.
This fixes #19