On 27 Mar 2003 at 7:21, Andrew Bartlett wrote: > On Thu, Mar 27, 2003 at 01:27:26AM +0000, Andrew Bartlett wrote: > > On Wed, Mar 26, 2003 at 04:11:13PM -0800, Shawn Wright wrote: > > > Ok, stupid me. Somehow I missed updating /lib/libnss_winbind.so on both > > > these machines. Presumably this would have also caused corruption of the > > > winbind idmap? > > > > I doubt it, actually. > > > > > Since winbind is now installed with a "make install", would it not be a good > > > idea to also install libnss_winbind.so also? Or at least provide some version > > > checking in winbind so that it will fail to start and report an error if it > > > encounters the wrong version of libnss_winbind.so? > > > > Winbind doens't *require* libnss_winbind - there are actually situations where > > it is used without it. That said, I've implemented some extensive version > > checks from the client side - we certainly won't connect to a winbind with > > a different protocol version any more. > > (In Samba 3.0 and Samba HEAD) > > In Samba 2.2 we have a more basic check, but it should still cause the client to > bail if contacting the wrong version.
Sorry for my ignorance, but I'm not sure what you mean by client here, but assume winbind is a client to nss? I do know that winbind from 2.2.8 *did* run with libnss_winbind.so v2.2.5 in place, resulting in broken getent passwd output, where only domain user ids were shown. Putting the libnss_winbind.so from v2.2.8 was all that was required to fix the problem... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Shawn Wright, Systems Manager Shawnigan Lake School http://www.sls.bc.ca [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba