Comment 12 for bug 1007293

On Tue, Jun 05, 2012 at 02:25:02PM -0000, vagk wrote:
> I changed the interfaces file to get static ip and retried.

This should not matter because dhclient doesn't return control to ifupdown
until it successfully acquires an IP.

> It failed but for a different reason.

> My /etc/yp.conf has no direct ip but a cname
> ypserver nisserver

> When networking got up /etc/resolv.conf was empty and that is because
> resolvconf package deleted the information that the last dhclient command
> wrote to /etc/resolv.conf

That's because you had invalid network configuration information: you were
no longer using DHCP, but had not specified another source for DNS server
information.

> So I removed package resolvconf (which I don't like in lab setups, same
> as network-manager) and voila!

resolvconf is the supported mechanism for managing /etc/resolv.conf in
12.04. Outside of your experiments here for debugging, I strongly advise
that you keep it installed.

> I rebooted and now I there was a 10 second delay before lightdm started
> and ypbind got running.

What is the system doing during this 10 second delay?

> Static IP on /etc/network/interfaces and nis server by IP in /etc/yp.conf
> works (or by cname and without resolvconf package)

> IP from dhcp on /etc/network/interfaces does not work. It seems that
> ypbind starts before networking

I'm still lacking the debugging information to see why it's starting before
networking for you. For that I need to see the syslog output of a boot with
--verbose.