Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

univention-samba4-backup: don't touch backups every day #57

Open
wants to merge 1 commit into
base: 5.2-0
Choose a base branch
from

Conversation

SvenRoederer
Copy link

Please make sure you considered the following things

Link to the issue in Bugzilla

https://forge.univention.org/bugzilla/show_bug.cgi?id=57409

Description of the changes

The backups get their permissions changed every time the script is running. This changes the ctime of the file and causes inclusion to systembackups (e.g. bareos). This is especially annoying when many backupfiles are kept or the files are large.

This change uses find to only change the permission, where they are not as expected.

Tested with UCS-5.0-8

@CLAassistant
Copy link

CLAassistant commented Jun 28, 2024

CLA assistant check
All committers have signed the CLA.

The backups get their permissions changed every time the script is running. This changes the ctime of the file and causes inclusion to systembackups (e.g. bareos). This is especially annoying when many backupfiles are kept or the files are large.

In f065824 calling "chmod" for every files was added, now we do it only for files with wrong permissions.
@SvenRoederer
Copy link
Author

updated the Code as suggested by @JuergenBS

@SvenRoederer
Copy link
Author

@JuergenBS ping - Any update?
I added this patch on my local system, after making this PR. 5 Days ago I installed the most recent updates of 5.1-9 (errata1140) and realized that the backups still include all files of the backup-folder again. Seeing this in UCS 5.2 and also backported to 5.0 would be great.

@reqa
Copy link
Member

reqa commented Oct 17, 2024

Thanks for the ping and the improvement suggestion, we'll look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants