Hm, that's interesting. Because when I turned of NetworkManager in past releases, NIS just worked fine. In Hardy beta, when I turn of NetworkManager NIS never comes up; I assumed that was because it was listening on dbus for NetworkManager to tell it the interface was available. I had to add the -no-dbus flag to YPBINDFLAGS in /etc/default/nis to get NIS to start working again.
Is THAT a bug, then? Really, I think all the need to continually internalize GNU/Linux specific features like dbus and networkmanager into portable, generic, veteran tools like NIS and automount shows that we're going the wrong way. Maybe, as you say, the solution is to integrate upstart with networkmanager/dbus, then fix these tools to use upstart instead of sysv init, and keep the dependency external that way. Another option, that might be simpler, would be to create some kind of command-line interface to dbus/networkmanager, so that we could wrap a script or program around the startup of these network services that would wait for the proper events then start them up. It would be a generic utility so it could be used for ANY tool, without having to modify them all one by one. Is there a Perl or similar interface to dbus? It just annoys me that we seem to be marching full speed into a networkmanager-controls-the-universe world, without really considering everything that is impacted by this. Sure, it's great for laptop users but what about the rest of us? But I suppose this bug report isn't the place to discuss that. -- 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
