This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: nss_compat in glibc-2.2.3 (Was: static binaries & netgroups)
- To: Andreas Jaeger <aj at suse dot de>
- Subject: Re: nss_compat in glibc-2.2.3 (Was: static binaries & netgroups)
- From: Torsten Duwe <duwe at caldera dot de>
- Date: Tue, 5 Jun 2001 11:42:21 +0200 (CEST)
- Cc: Torsten dot Duwe at caldera dot de, "H . J . Lu" <hjl at valinux dot com>, libc-alpha at sources dot redhat dot com
- References: <200102151556.QAA21140@ns.caldera.de><20010215094356.A3353@valinux.com><14989.24250.474023.584488@ns.caldera.de><20010216091332.A20320@valinux.com><15124.54408.572938.625919@ns.caldera.de><m3snhnjdf7.fsf@D139.suse.de><15124.56194.583339.568099@ns.caldera.de><m3y9rfhxd2.fsf@D139.suse.de>
- Reply-to: Torsten dot Duwe at caldera dot de
Andreas> I don't advise to use that version without further patches, have
Andreas> a look through CVS first and apply at least the appended patch -
Andreas> but there might be more problems.
Indeed there are. But first for the good news: the original problem (using
compat on passwd, having netgroups in it, calling getpw* from a static prog
=> crash) is gone in the 2001-05-31 snapshot; nss_compat now works like a
charm. Thanks a lot to whoever fixed this ! (even if it was unintentionally
;-)
Yes, a quick build with the patch you included in a previous mail fixed the
nss_compat, and yes, this build caused NFS mounts on ia32/linux to lock up. I
didn't track it down whether it was because of
"*sysdeps/i386/i486/atomicity.h (exchange_and_add)", but went for said
full-blown cvs snapshot build instead, which also worked a lot better in this
respect ;-]
Logical question: with at least these problems known, are the release gurus
thinking about a bugfix version, call it 2.2.3.1 (Hi, H.J.L ;-) or 2.2.4 ?
Especially since it's a critical component in the LSB spec draft...
Thoughts ?
Torsten