This is not really a Seafile issue but I hope for some support here in the Forum.
Maybe someone tried something similar already and ran into a similar issue.
The following scenario:
Seafile server 6.2.5 on an Ubuntu 16.04 RootServer --> cloud.example.com
Inside my home network: A Helios4 NAS system with ARM processor and Openmediavault (OMV) is running with Samba shares and seaf-cli installed.
On the Helios4 a headless seaf-cli is running under the user “seafile”.
The Seafile Server cloud.example.com shares Library1.
The seaf-cli on the Helios4 syncs Library1 to a Samba share folder “Samba1”.
Samba1 is shared as read/write to the users seafile, user1 and user2.
The sync of Library1 works flawless. All files of Library1 are synced to Samba1.
A ls -l in Samba1 shows the permissions to be:
drwxr-sr-x 2 seafile users 4096 Apr 2 08:24 Folder1
-rw-r–r-- 1 seafile users 452334049 Mar 29 09:45 Movie1.MOV
-rw-r–r-- 1 seafile users 422486 Mar 29 10:42 Word.docx
-rw-r–r-- 1 seafile users 433303 Mar 14 17:46 Letter.pdf
If I access the files as user1 or user2 from a Mac inside the share Samba1 I can’t edit the files which were written by seaf-cli under user seafile, but can open/read them.
If I access the files as the user seafile from the same Mac inside the Samba1 then I can edit the files which were written by seaf-cli under user seafile. So can read/write.
It looks like user1 and user2 only have read permissions on the files that were written by user seafile through seaf-cli application.
BUT once I changed a file with the user seafile from the Mac inside Samba1 then I can edit the files also with user1 and user2 inside Samba1.
So it seems that the files written by user seafile thorugh the application seaf-cli makes them read only for user1 and user2 BUT files written by user seafile directly inside the share Samba1 gives them “read/write” permissions also for user1 and user2.
What can I do so that the application seaf-cli can write under the user seafile into the Samba1 and that user1 and user2 can actually have read/write permissions on them inside Samba1, as intended.
I hope this all makes sense.
In a nutshell:
Files written into a Samba share by seaf-cli are always read only for other users that access the share through Samba, although they should have read/write permissions on the files in the share.
What can be done to have the files read/write for all users, although written by seaf-cli application.