[Samba] s3fs and symlinks

[steve]

On 04/07/12 01:42, Andrew Bartlett wrote:
> On Tue, 2012-07-03 at 15:14 +0200, steve wrote:
>> On 03/07/12 14:33, Volker Lendecke wrote:
>>> On Tue, Jul 03, 2012 at 12:48:26PM +0200, steve wrote:
>>>> Hi everyone
>>>>
>>>> I have a problem with S4 following symlinks.
>>>>
>>>> In windows, I can access a share ¡f the the path is the actual
>>>> directory but not if the share contains a symlink to the same
>>>> directory. I get access errors.
>>>>
>>>> In Linux under NFS, I can access the share either directly via the symlink.
>>>>
>>>> Does s3fs understand symlinks at the moment?
>>>
>>> Look for "wide links", "unix extensions" and "allow insecure
>>> wide links" in "man smb.conf".
>>>
>>> Volker
>>>
>> Hi Volker
>> Unfortunately, wide links (which I think is what I need) doesn't work:
>> samba-tool testparm
>> Unknown parameter encountered: "wide links"
>> Ignoring unknown parameter "wide links"
>> Press enter to see a dump of your service definitions
>>
>> and samba_spnupdate throws errors too.
>
> Regardless of the errors, they will still work.  We have two loadparm
> engines, and we have not yet reconciled them.  It remains a tedious job
> that hasn't yet been finished.
>
> To check if a parameter is accepted by the file server component, run
> 'testparm' rather than 'samba-tool testparm'.
>
> Andrew Bartlett
>
Hi Andrew, hi everyone
I didn't know about testparm without samba-tool.

With:
wide links = Yes
in [global]
testparm is clean
BUT, the symlink gives Access is denied.

Here is the share containing the symlinks:
[students]
path = /home2/students/data
read only = No

Here is an example of the symlink in /home2/students/data pointing to 
the actual data:
lrwxrwxrwx 1 root root 30 Jul  4 09:51 brian -> 
/home2/students/year7/7a/brian

Here is an example of the actual data:
drwxr-xr-x 21 brian       Domain Users 4096 Jul  4 10:24 brian

If the share points at the actual data, we are allowed access. If the 
share points to the links, we get Access is denied.

What have I done wrong?
Cheers, Steve