So, does this mean that the only way to get symbolic links working in samba shares accessed by Windows clients is to create a security hole?
So, does this mean that the only way to get symbolic links working in samba shares accessed by Windows clients is to create a security hole?
Thank you for posting the solution. Life is good now.
After updating to 10.04 it broke my symlinks. I have already added the 3 setting mentioned before. Any suggestions?
and 3 sec after i post i figure it out!
Thanks anyways.
never mind.
Last edited by neutron68; May 6th, 2010 at 04:29 AM. Reason: duplicate response
OK, here's what worked for me. From an article at:
http://www.jonathanmoeller.com/screed/?p=1590
I ran smbpasswd and mine started working.
I had already installed via Synaptic and had configured using the gui tool.
Worked for me.
Simply add "unix extensions = no" into the [global] section of smb.conf
Just a remark for those gotten bitten by this behavior, and want to avoid similar occurrences in the future: The samba team doesn't read distribution's bug trackers and forums, but they do have their own list:
samba-technical@lists.samba.org
The samba team lives under the impression that only a tiny minority of people are affected by this bug, and they can only be convinced otherwise if more people make their voices heard. So if you care, drop a note to samba-technical@lists.samba.org
Thanks,
Alain
I ended up using these three options in the global sections:
follow symlinks = yes
wide links - yes
unix extensions = no
This was the only way that I could follow sym links in Lucid that previously worked in 8.04.
Bookmarks