I believe this bug is fixed in Hardy. There's a new version of NIS's ypbind that uses dbus to connect to networkmanager and doesn't bind until after the network interface is brought up.
Once I modified my /etc/yp.conf to use an IP address instead of a hostname (I know the comments there say you should, but before networkmanager it used to work fine to have a hostname, because DNS was always running as soon as dhcp configured the interface, which always happened before NIS was started) I was able to boot and have nis started properly. However, this is not the end of the story, although I will open other bugs for the rest. There are still other facilities on a typical enterprise desktop that rely on NIS (in particular I'm thinking of autofs here) which FAIL TO START in Hardy, because of this fix. Yeesh. -- nis daemon fails to attach to domain the first time it is run in Gutsy https://bugs.launchpad.net/bugs/152794 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
