[Bug 569757] Re: NIS upstart dependency broken for lucid

[Jeremy Yoder]

Is that change to CRON backported to Lucid?  I'm guessing not, but that
would be nice.

As for gdm/lightdm/atd I think the crucial one there is atd.  The login
stuff probably takes long enough to start that NIS will be up by then
(plus that's nowhere near an exhaustive list of *dm's and adding all of
them is probably the wrong way to go).

I'm torn on whether to add the upstart wrappers or completely replace
init.d with upstart in Lucid.  I guess I'd lean towards the more minimal
change to Lucid and having the new system in Precise, but I defer to
your expertise.  As long as one of them happens I think we're good.

Somehow I missed Clint's reply to my message, but since NIS is pretty
darn hosed in Lucid without one of these workarounds, I can't see how
anyone would mind it actually working out of the box.  Even if the
change breaks the duct tape things people have done for 2 years to work
around this bug, at least they can back those things out once and count
on it not breaking again.  Also, the type of people who are really going
to care are going to check the changelogs before they update :)

Thanks guys!

-- 
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