Harald Hoyer wrote: > redhat@xxxxxxxx wrote: >> And there it hangs until i ^C "udev_start". >> (Ofcourse start_udev can't access the network so early in the boot >> process). > > grrr... this seems to be glibc and getpwnam(3) I also have a (perhaps unrelated) issue with udev_start hanging at boot time until I hit ^C. Running it with strace revealed that a subprocess spawned by udev_start tries to log through syslog to complain about a missing environment variable: Sep 22 02:38:31 beetle hal.hotplug[17028]: SEQNUM is not set As a sidenote, I've always found the way processes hang when syslogd isn't running extremely annoying. Is this a bug in glibc's implementation of syslog(2) or this behavior by design? -- // Bernardo Innocenti - Develer S.r.l., R&D dept. \X/ http://www.develer.com/ -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
