Comment 21 for bug 569757

On Feb 7, 2011, at 4:03 PM, Maciej Puzio <email address hidden> wrote:

> On my mail server postfix and dovecot depend on nis. Currently this
> particular dependency is handled properly, because all three daemons are
> started by means of /etc/rc?.d in the correct order. Please correct me
> if I am wrong, but I worry that the solution suggested by Clint Byrum in
> #18 might cause nis to race with postfix or, if postfix is converted to
> "native upstart", with dovecot.

Right, good point. I've been monkeying with this, and i think the real need is to be able to make sure that anything that needs access to users and groups is blocked by nis, or ldap, or winbind, or puppet... Whatever you use to provide users and groups, has to run first.

The appropriate thing to do is to Develop a policy of variable exporting in upstart jobs.

env NEEDS_ID=1
export NEEDS_ID

adding that to all the services that need Ident would be awfully painful. But having the generic network-services job that has been proposed set it would allow us to just have postfix follow that job, and have nis, winbind, etc use

start on starting NEEDS_ID=1

If something else like autofs needs to start before generic network services it will have to export this variable. This decouples the consumers and providers.

>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/569757
>
> Title:
> NIS upstart dependancy broken for lucid
>
> Status in “nis” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: nis
>
> NIS does not work on lucid: without upstart, it starts anytime,
> unrelated to net-device-up events. If the passwd/shadow is provided
> through NIS, it seems completly random, whether username resolution is
> provided to gdm.
>
> The only fix seems an upstart startscript.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscribe