When you add a new user or group via samba, samba needs to assign it a
uid / gid The next available
number can be stored in the ldap server and queried/updated by samba.
I create my users / groups outside of samba and so don't use it so I'm
not sure exactly
what should go here. There's a sambaUnixIdPool object class in the
samba.schema
which could hold these values and by the look of the example, I'm
guessing that objectClass
will be added to your sambaDomain object in the ldap server.
If you do an ldap search on your server for '(sambaDomain=*)' you should
see your domain and
it should have objectclass sambaDomain and objectClass sambaUnixIdPool
the dn of this entry is where you're telling smbldap.conf to store the
uid / gid numbers.
Hope this helps
Duncan
listserv.traffic@sloop.net wrote:> Quick question:
>
> In the Samba-by-example, (Chapter 5, Page 188 of PDF)
>
> ---quote---
> 4. Edit the /etc/smbldap-tools/smbldap.conf file so that the following
information is changed from:
>
> # Where to store next uidNumber and gidNumber available
> sambaUnixIdPooldn="cn=NextFreeUnixId,${suffix}"
>
> to read, after modification:
> # Where to store next uidNumber and gidNumber available
> #sambaUnixIdPooldn="cn=NextFreeUnixId,${suffix}"
> sambaUnixIdPooldn="sambaDomainName=MEGANET2,dc=abmas,dc=biz"
>
> ---quote---
>
> I don't understand what the purpose is, or more precisely what it is
> this accomplishes. Could someone explain it to me?
>
> I'm making good progress, but still hashing things out.
>
> TIA
> -Greg
>
>