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

syncOwnership skip parent folders of an included file #9540

Closed
glaudano opened this issue May 16, 2024 · 2 comments
Closed

syncOwnership skip parent folders of an included file #9540

glaudano opened this issue May 16, 2024 · 2 comments
Labels
bug A problem with current functionality, as opposed to missing functionality (enhancement) needs-triage New issues needed to be validated

Comments

@glaudano
Copy link

What happened?

I'm synching users home directories running as syncthing user (with syncthing group) with CAP_CHOWN and CAP_FOWNER enabled by systemd unit override.
Almost everything is running as expected but, using this exclusion schema:
!.ssh
!.config/gtk-3.0/bookmarks
.*

The .ssh folder and files inside the folder has expected ownership (glaudano:users)

The file .config/gtk-3.0/bookmarks has expected ownership (glaudano:users)

The folders .config and .config/gtk-3.0 keep syncthing:syncthing

Syncthing version

1.27.7

Platform & operating system

Debian Linux 12.5

Browser version

No response

Relevant log output

No response

@glaudano glaudano added bug A problem with current functionality, as opposed to missing functionality (enhancement) needs-triage New issues needed to be validated labels May 16, 2024
@glaudano glaudano changed the title syncOwnership skip folders of an included file syncOwnership skip parent folders of an included file May 16, 2024
@tomasz1986
Copy link
Contributor

I think this may be the same problem as #8735.

@glaudano
Copy link
Author

Yep! The solution provided in #8735 makes the sync behave as expected. Many thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A problem with current functionality, as opposed to missing functionality (enhancement) needs-triage New issues needed to be validated
Projects
None yet
Development

No branches or pull requests

2 participants