Description of problem:
vol_id attemps to drop privileges to that of the 'nobody' user when it runs, by
switching to the 'nogroup' gid and the 'nobody' uid. This fails on Fedora
because we don't have a 'nogroup' group. (It also creates boot delays when
network-using nsswitch modules are in use, but that's a side-effect.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Switch on "ldap" for use in "group" lookups in /etc/nsswitch.conf, preferably
with a default /etc/ldap.conf on the system.
Debug spew as vol_id tries to look up information about the group.
Why not just use the user's primary group ID?
Created attachment 124586 [details]
patch to use "nobody"'s primary group instead of assuming that it's named "nogroup" and going from there
Very good suggestion! Thank you for the patch! :)
*** Bug 182700 has been marked as a duplicate of this bug. ***
will this hit rawhide anytime soon or is there a test rpm somewhere?
already should have with udev-084-4
So in other words you're saying that something completely different is causing
boot issues with udev and LDAP? How do we debug this?
Hm ok... the vol_id error went away here with current udev release but now there
are lots of other errors... Could this by any chance be
related/affected/affecting bug #181305?
With latest udev 084-6 everyting is working. This bug can be closed imho. Thanks.