preserve the owner, group and umask #1454
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
when migrating the configuration files to their new location.
killing
added a commit
that referenced
this pull request
Nov 19, 2015
preserve the owner, group and umask
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 is a follow up pull request to the already closed issue #1429 The problem is not on the users end. It's the way the upgrade Script moves the config files to the new locations.
The upgrade script does copy the configs like this
If you execute the upgrade script with root priviliges the copied filed will have the rights of the user logged in (in this case root).
The correct way would be to preserve the owner, group and umask