logo       

nss-ldap: *** glibc detected *** free(): invalid next size (normal):: msg#00017

ldap.padl.nss

Subject: nss-ldap: *** glibc detected *** free(): invalid next size (normal):

Client: nss_ldap-2.48 + 2.49 on kubuntu 5.10 ia32
LDAP-Server: Win2003-R2
______________________
- with: nss_map_attribute uniqueMember msSFU30PosixMember
no error

-with: nss_map_attribute uniqueMember member
.
correct output
.
group123:*:10056:user1,user2,user3
*** glibc detected *** free(): invalid next size (normal): 0x080584f8 ***
Aborted
__________________________

1st is official in config , 2nd should also work.
The group data in AD are the same twice with different attribute types. With the 2nd you have only to give a gid for groups and can manage all users with the official windows group membership (attr: member) one times and not twice (member + msSFU30PosixMember).
The windows group manager wizard allows nested groups also only with members, not with msSFU30PosixMember.
______________________
config:
nss_map_objectclass posixAccount User
nss_map_objectclass shadowAccount User
nss_map_attribute uid sAMAccountName
nss_map_attribute cn sAMAccountName
nss_map_attribute userPasswort unixPassword
nss_map_attribute homeDirectory unixHomeDirectory
nss_map_objectclass posixGroup Group
pam_login_attribute sAMAccountName
pam_filter objectclass=User
pam_password ad

nss_map_attribute uniqueMember member = o.k.
-or-
nss_map_attribute uniqueMember msSFU30PosixMember = error
__________________________

If anyone of from the developers need more debugging output please tell me how I can produce this.

Thanks.
Steffen





<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise