4.1.9 CIFS following symbolic links outside of share

[jasg]

Hi,
After the recent upgrade to 4.1.9 my ReadyNas DUO will not follow symbolic links which link to a directory outside of the share they are in.

Prior to this update, this has always worked fine.

Can someone please give me some pointers as to how I can enable this on my ReadyNAS?

(I did have another thread related to this, but now that I understand the problem a bit better, I thought it would be best to start a more specific question in a new thread)

Many Thanks
J

[Slasky]

This might be linked to the issues known to happen in 4.1.9 with share permissions. Can you access the shares themselves without any problems?

[jasg]

Yep, I can access the shares the links point to directly.
Just not via the link

If I create a symbolic link which points to within the same share then I can follow this no problem.

[eanrollings]

I can confirm this issue after said update.

...however I just fixed it by editing my smb.conf file (located in: /etc/samba)
and added a "true" setting for "wide links":

[global]
...
 follow symlinks = 1
 wide links = 1
...

works like a charm again 🙂

FYI, while I was sleuthing for a fix, I did come across this: http://www.linuxquestions.org/questions/linux-software-2/samba-client-wont-follow-sym-links-801633/
which seemed to make me think that I also needed to add the "unix extensions = no" setting. It seems to work without it, so not sure if this setting is needed.

and for reference, there's always RTFM: http://www.samba.org/samba/docs/using_samba/ch08.html

hope this helps others!

[mdgm-ntgr]

That change has nothing to do with 4.1.9 ownership/permission issues. The disabling of wide links was a change made in samba for security reasons. It's not recommended to override that change. 4.1.9 included a major samba update from 3.0.37 to 3.5.15.

If you are suffering from ownership/permissions issues on 4.1.9 please consider updating to 4.1.10: http://www.readynas.com/forum/viewtopic.php?f=17&t=59222

[jasg]

eanrollings wrote:

I can confirm this issue after said update. ...however I just fixed it by editing my smb.conf file (located in: /etc/samba) and added a "true" setting for "wide links": [global] ... follow symlinks = 1 wide links = 1 ... works like a charm again 🙂 FYI, while I was sleuthing for a fix, I did come across this: http://www.linuxquestions.org/questions ... ks-801633/ which seemed to make me think that I also needed to add the "unix extensions = no" setting. It seems to work without it, so not sure if this setting is needed. and for reference, there's always RTFM: http://www.samba.org/samba/docs/using_samba/ch08.html hope this helps others!

Worked for me, thanks