umask in prune command #69
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#69
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When one repo is used with more clients (umask 007) prune change repository files permissions using default mask (077) and then other clients cant make backups.
In file prune.py in full_command --umask should be added when used different than default.
Thanks for reporting! Makes sense to me. Do you think there's ever a use case for different umasks for create and prune? Or do you think they'd always be the same?
I think it can be the same umask variable used. I don't see any cases for different umasks - created and modified backup repository should always have the same files permissions.
This is now implemented, and just released as part of borgmatic version 1.2.0! Enjoy.