netgroup: nis in nsswitch.conf causes libc6 to fail and programs like sudo or rpc.mountd to crash

Bug #49677 reported by D2K
8
Affects Status Importance Assigned to Milestone
GLibC
Fix Released
Undecided
Unassigned
glibc (Ubuntu)
Fix Released
Undecided
Unassigned
nis (Debian)
Fix Released
Unknown

Bug Description

if in /etc/exports

/export/bml_nobackup @local_hosts(rw,sync)

then e.g. rpc.mountd fails:

root@corona-nh:/etc# /etc/init.d/nfs-user-server restart
Stopping NFS servers: mountd nfsd.
Starting NFS servers: nfsd mountd.
root@corona-nh:/etc# rpc.nfsd: nss_nis/nis-netgrp.c:78: _nss_nis_setnetgrent: Assertion `len > 0' failed.

If I set

/export/bml_nobackup corona-nh(rw,sync)

everything runs okay.

Same as bug:#369536 in Debian: http://lists.debian.org/debian-glibc/2006/05/msg00385.html

Changed in nis:
status: Unknown → Unconfirmed
Revision history for this message
TLE (k-nielsen81) wrote :

Hallo, Thank you for reporting this bug.

Is this bug still present in Edgy ?
Regards TLE

Changed in glibc:
status: Unknown → Unconfirmed
Revision history for this message
D2K (david-hellier-csiro) wrote :

This bug appears to be fixed in edgy.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Marking as "Fixed released" based on DTK's comment (with guidance from Luka).

Changed in glibc:
status: Unconfirmed → Fix Released
Revision history for this message
TLE (k-nielsen81) wrote :

Great. What about those upstream bugs. Should we do anything with them ?
\TLE

Revision history for this message
Peter Whittaker (pwwnow) wrote :

I believe it would be up to Debian users to determine whether this bug is still present in Debian, and to update the upstream report accordingly. There are Debian users in the Ubuntu community, so this may or may not get noticed from Launchpad and addressed in debbugs.

Likewise an Ubuntu glibc developer might verify the GNU sources and act accordingly.

But since the bug is no longer present in Ubuntu, there isn't much more we can do from here.

Revision history for this message
Jeff Bailey (jbailey) wrote :

Well, the upstream bug was linked incorrectly to Debian. I disconnected it and marked it as fix released. Since our package inherits directly from upstream, that task can be safely closed. The tracking bug on Debian will update as Debian fixes it in their archive. As they're in freeze for release, I wouldn't expect that they'll update soon, though.

Tks,
Jeff Bailey

Changed in glibc:
status: Unconfirmed → Fix Released
Changed in nis:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.