> The problem here is that the user id 3816 is shared by a number of > users. The client library is just expecting one response and closes the > connection after reading the first response (mmoreda in this case). The > two other users can probably be written by nslcd before any error > because of buffering. > > The NSS interfaces do not properly support multiple users with the same > numeric user id (or with the same username for that matter). At least > nscd seems to have issues with such set-ups. > > If you cannot give each user a unique numeric user id and you are aware > of the security implications of this set-up you could just ignore these > errors. The errors do not cause any problems and things should just > work. > > A way to avoid the errors is to make a dummy user in /etc/passwd with > numeric uid 3816. This would ensure that all reverse lookups like the > above will not hit nslcd (this is even a slight performance > improvement). > > If you have no additional information for this bug I plan to close it in > a couple of days. Thanks for the clear bug report, especially the debug > information made it easy to pinpoint. > > Hope this helps, > > -- > -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
Hi there! Thank you so much for your information. Last days I was suspecting this not being a bug but a configuration problem somewhere. I don't want to have users with same UIDs at all. You found it for me, so thanks again. Please keep developing nslcd. Best regards. PD: It's me or nslcd package is recommending nscd? I don't understand why, and I purge nscd when I see it installed. PD2: arthur==arturo :) -- # # Arturo Borrero Gonzalez || cer.i...@linuxmail.org # Use debian gnu/linux! # -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
