This is a discussion on [Samba] winbind enum users = yes, but: is there a limit? - Samba ; I am seeing odd behaviour with winbindd 3.0.21c on Red Hat Enterprise Linux 4, with idmap_ad. I have 'winbind enum users =3D yes', mainly for performance and load evaluation purposes, since my AD setup currently has 8500 or so users ...
I am seeing odd behaviour with winbindd 3.0.21c on Red Hat Enterprise
Linux 4, with idmap_ad.
I have 'winbind enum users =3D yes', mainly for performance and load
evaluation purposes, since my AD setup currently has 8500 or so users
and in production will have many more. Only *one* of those users has
uidNumber, gidNumber, set to make it usable in the Linux environment.
When I say
getent passwd RABOTESTEU-gautierb
I see the entry for that user, but if I say
I notice that source/nsswitch/winbindd_user.c contains a constant
MAX_GETPWENT_USERS which is set to 500. Could that be biting me? It
looks as if that constant is simply a 'batch size' (max number of users
to return per call?) but the loop that it controls seems to assume that
every user will have valid Linux attributes, which is not the case for
me. I think it will be causing lots of *empty* responses to be returned
to the client -- could that be causing confusion?
In any case, I'd be grateful for any suggestions as to where to look.
This email (including any attachments to it) is confidential, legally pri=
vileged, subject to copyright and is sent for the personal attention of t=
he intended recipient only. If you have received this email in error, ple=
ase advise us immediately and delete it. You are notified that disclosing=
, copying, distributing or taking any action in reliance on the contents =
of this information is strictly prohibited. Although we have taken reason=
able precautions to ensure no viruses are present in this email, we canno=
t accept responsibility for any loss or damage arising from the viruses i=
n this email or attachments. We exclude any liability for the content of =
this email, or for the consequences of any actions taken on the basis of =
the information provided in this email or its attachments, unless that in=
formation is subsequently confirmed in writing. If this email contains an=
=20offer, that should be considered as an invitation to treat.
To unsubscribe from this list go to the following URL and read the