A follow-up to the sync, here's what I've found for these 4 groups: admin - gid 23 - This group exists in ldap and userbase. There is also an entry in /etc/group (with gid 115) in bcfg2 that causes "getent group admin" to return a group with no members on most MCS machines. "getent group 23" returns the group with members. ***** # admin, groups, mcs.anl.gov dn: cn=admin,ou=groups,dc=mcs,dc=anl,dc=gov objectClass: top objectClass: posixGroup memberUid: cschmitz memberUid: jhedden memberUid: leggett memberUid: maxadam memberUid: stace memberUid: valdes memberUid: winkler memberUid: raffenet memberUid: hunter memberUid: dolson gidNumber: 23 cn: admin admins - gid 1001 - Only exists in ldap ****** # admins, groups, mcs.anl.gov dn: cn=admins,ou=groups,dc=mcs,dc=anl,dc=gov objectClass: posixGroup objectClass: top cn: admins gidNumber: 1001 memberUid: grog memberUid: leggett memberUid: papka memberUid: sneedham memberUid: forero wheel - gid 0 - Exists in ldap and userbase ***** # wheel, groups, mcs.anl.gov dn: cn=wheel,ou=groups,dc=mcs,dc=anl,dc=gov objectClass: top objectClass: posixGroup memberUid: cschmitz memberUid: maxadam memberUid: stace memberUid: valdes memberUid: winkler memberUid: raffenet memberUid: dolson memberUid: hunter memberUid: jhedden memberUid: leggett memberUid: roberts gidNumber: 0 cn: wheel sysadmin - gid 14 - Exists in ldap and userbase. Is empty. -- Ken Raffenetti Systems Administration Associate MCS Division - Argonne National Laboratory