Discussed with Steve on IRC, and we confirmed that the assumption that
this is the rc-sysinit change is probably false. Prior to 11.10, the rc-
sysinit start on condition was
start on filesystem and net-device-up IFACE=lo
So in the case of a NetworkManager only system, runlevel 2 is reached at
precisely the same point as before.
My guess is that this has always been racing with network-manager, and
somewhere between 11.04 and 11.10, we changed things enough that rc-
sysinit + everything in /etc/rc2.d/S* before nfs-kernel-server overtook
network-manager, which does start very early (local-filesystems and
started dbus), so this seems quite feasible.
Since all listening is, by default, on 0.0.0.0 (::0 for ipv6) then I
have to wonder if you have it binding to a specific interface (possibly
py pssing -H some.host.name in /etc/default/nfs-kernel-server in
RPCNFSDOPTS).
If so, it may be preferrable for you to move the configuration of that
interface to /etc/network/interfaces to prevent this type of race
condition.
Either way, I don't believe this is due to the rc-sysinit change, so I'm
moving the status of this back to New, though keeping myself assigned.
** Changed in: ifupdown (Ubuntu)
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848823
Title:
if all interfaces are configured via NM, static-network-up emitted
when only lo is configured
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/848823/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
