I've taken on the task of trying to get this fixed for precise using native and idiomatic upstart jobs for each of the services. It's not directly backportable to lucid, as it depends on upstart's wait-for- state generic helper instead of doing things directly in the nis-wait job, adds a versioned dependency on rpcbind for upstart support in that package, and references the 'failsafe-boot' event. The first of these can be addressed for backporting by using Jeremy's implementation, and the second can use an alternative dependency on the upstart-enabled portmap package. The third can be replaced with 'network-device-up INTERFACE!=lo', I guess.
Honestly if I'd had the sense to read through the bug log all the way to the end before poking at this, I think I would've just gone with Jeremy's implementation. But now having gone to the effort of splitting the init script up into proper per-service upstart jobs, I think that's the better way forward for precise rather than a halfway measure of a nis-sysv job. I've pushed these changes to lp:ubuntu/nis. Clint, what do you think? If we're introducing upstart jobs in an SRU anyway, I'm not sure it matters terribly if we're completely removing the init script vs. wrapping it, so I think it would be better to go all the way and avoid having to do two separate init script transitions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
