Comment 13 for bug 134716
Revision history for this message
| Max-Ulrich Farber (maxulrichfarber) wrote | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I have the same problem when 'unix extensions = yes' is set on the Samba server side. Server and client are both Ubuntu 7.10 (Gutsy).
If the symlink itself is the share, it can be accessed from the client, and it is followed correctly on the server. The symbol for the share in the clients GUI is not that of a link but that of a simple folder or file.
If the share is a folder and she symlink is inside the share, the symlink is displayed as a symlink on the client. It can't be followed on the server because the client tries to follow the link on the client itself. Usulally the target does not exist there and the link is displayed as 'broken', but it if a file with the targets name occasionally exists on the client, the link leads to a wrong file. That can be quite dangerous.
The problem only depends on the setting of 'linux extensions = yes' on the server; it is the same if the share is mounted with 'smbfs' or with 'cifs' on the client.
Setting 'unix extensions = no' on the server side seems to me not to be a good solution, for usually unix extensions = yes is needed for access rights administration. I hope that there will soon be an other fix for this bug.