iLikeWaffles
Dabbler
- Joined
- Oct 18, 2019
- Messages
- 15
Hi,
I have a dataset assigned to syncthing and on it's own it works fine. I have added this dataset to smb shares and after some permission twiddling, managed to get both to sort of coexist.
However, whenever the smbuser writes a new file to the dataset though samba, this new file is owned by the smbuser. Syncthing is unable to synchronize this file.
I have made a temporary workaround in the form of a cronjob that chowns every file on the shared dataset back to being owned by the syncthg user, but I feel this is the wrong solution.
Assuming that both SMB and syncthing will need to do reads and writes on this share, what's the recommended configuration for allowing both equal access to the dataset, without periodic chowning?
I have a dataset assigned to syncthing and on it's own it works fine. I have added this dataset to smb shares and after some permission twiddling, managed to get both to sort of coexist.
However, whenever the smbuser writes a new file to the dataset though samba, this new file is owned by the smbuser. Syncthing is unable to synchronize this file.
I have made a temporary workaround in the form of a cronjob that chowns every file on the shared dataset back to being owned by the syncthg user, but I feel this is the wrong solution.
Assuming that both SMB and syncthing will need to do reads and writes on this share, what's the recommended configuration for allowing both equal access to the dataset, without periodic chowning?