Comment 2 for bug 862928

Revision history for this message
Clint Byrum (clint-fewbar) wrote : Re: NFS filesystems are not exported after booting

Hi John, man, sounds like you've been through the ringer on this one.

First off, if you have a truly static network connection that you always expect to be up on boot, I suggest using /etc/network/interfaces to define it. As of 11.10, the system will actually delay entering runlevel 2 (a.k.a. 'multiuser' mode) until all of these network interfaces are up. For earlier releases, one must modify /etc/init/rc-sysinit.conf to delay until the desired interface is up.

If you have a dynamic connection, things get trickier. I think there may be a solution here that has very little to do with upstart. When network-manager brings up interfaces, it looks in /etc/network/if-up.d and runs all those scripts for each interface. So the nfs-kernel-server package can add one of these which runs 'exportfs -a' each time an interface is brought up.

I really don't think its viable to involve bind9 or resolvconf in this situation. That is completely orthogonal to the issue of NFS not being able to export all of its exports because the network is not available.

Given all of that, I'm going to redirect this bug task to the nfs-utils package, as upstart really doesn't have anything to do with this particular issue.

Also I'm closing the upstream task. There's no deficiency in upstart itself that has been described here.