On Friday 21 February 2003 16:44, Matt Stamm wrote:
-> All users will have access to a public folder for shared files
-> All users have full read / write / execute permissions in the public folder.
I have something exactly like this, actually.
-> If the public folder is accessed through the link within each user's home folder then I do not get the full permission on files created within the public folder. The files end up belonging to the owner. The group has read access only. Why is this?
->If I map the pubic folder to drive L: this also works fine.
This is actually the expected behavior. Samba can control the permissions of files created for a share. By creating a symlink in a user's directory (e.g., /home/foo/public -> /home/public), you are going -around- Samba. The user simply changes to this directory and creates a file as if the directory belonged to the current user. Remember that that symlink is just that--a symlink. Samba can set the permissions for a share, but not a symlink. So this is why mapping the public share to another drive letter works: Samba is controlling the permissions. For a symlinked directory inside a user's home directory, the link is just another regular directory. [Perhaps I'm not explaining this well enough. It's Friday night, after all.]
It appears the link to the public folder is not the best idea. Is this the best way to do this? I would welcome any suggestions.
I'm sure there are many ways to do this. Brainstorm follows: 1. Create a Windows shortcut inside each user's home directory to \\samba\public . 2. Map \\samba\public to some drive letter (you need this) and create a Windows shortcut inside each user's home directory to that drive letter. This is what comes to me. Perhaps someone else has a better idea.