Samba4: wide links and unix extensions

[Michael Wood]

Hi

On 7 July 2012 13:27, Jelmer Vernooij <jelmer at samba.org> wrote:
> On Fri, Jul 06, 2012 at 07:48:49PM +0200, steve wrote:
>> On 06/07/12 18:40, Jelmer Vernooij wrote:
>> >On Fri, Jul 06, 2012 at 06:26:37PM +0200, steve wrote:
>> >>All my home directories are symlinks from a share to the real data.

Steve, your real problem is as follows, right?

You want to have your actual home directories in different locations
(e.g. on different disks) and not all in one directory.

i.e. instead of:

/home/user1
/home/user2
/home/user3

you want:

/home/staff/user1
/home/students/year1/1a/user2
/home/students/year2/2a/user3

etc.

but with winbind (if I understand correctly) you can only have
/home/${username}, even though AD can store a different path to the
home directory for each user.

Jelmer, someone on the samba list suggested the symlink approach.

I don't know the answers.  Just trying to clarify a bit.  I hope I
succeeded and that what I wrote is correct :)

>> >>I need wide links for windows clients to follow symlinks. To do
>> >>that, I must have
>> >>wide links = Yes
>> >>unix extensions = No
>> >>
>> >>This means that if I mount the share on a Linux clients, none of the
>> >>acl's are correct.
>> >>
>> >>I've seen bugzillas that were resolved on the same topic, but from
>> >>2010 and not with S4.
>> >>
>> >>Can we/do we plan to be able to have both server and client working
>> >>side to enable:
>> >>wide links = Yes
>> >>_and_
>> >>unix extensions = Yes
>> >Is there a particular reason you're using symbol links rather than
>> >e.g. a bind mount for your home directory?
>> >
>> >The consequence of disabling symbolic link support even when unix
>> >extensions are enabled (which is what you're asking) would also be that
>> >Linux clients wouldn't be able to create symbolic links on the share.
>> We aren't bothered about Linux clients creating more symlinks in the
>> share. We only want the admin to do that.
>>
>> The symlinks in the home share point at different folders.
>>
>> the home folder is:
>>  /home2/usuarios
>> the share is:
>>  [usuarios]
>> path = /home2/usuarios
>> read only  No
>>
>> The share contains symlinks to where the real home folders are e.g.
>> lrwxrwxrwx 1 root root 19 Jul  5 17:47 steve2 -> /home2/staff/steve2
>> lrwxrwxrwx 1 root root 32 Jul  4 13:07 stephen ->
>> /home2/students/year7/7a/stephen
>>
>> IOW staff have their home folder in /home2/staff, students in
>> /home2/students
>>
>> /home2/usuarios is just a pool of symlinks.
>>
>> The ldap directory looks like this:
>> unixHomeDirectory: /home2/usuarios/steve2
>> homeDrive: Z:
>> homeDirectory: \\server\usuarios\steve2
>>
>> It works OK with NFS for Linux clients and cifs for windows but
>> there is the odd share where we'd like to use cifs for both.
> How does it work okay with NFS? It doesn't follow symlinks for you
> either.
>
> Also, have you considered using bind mounts instead?
>
> Cheers,
>
> Jelmer

-- 
Michael Wood <esiotrot at gmail.com>