Comment 69 for bug 275451

Thanks MxxCon - your suggestion would have been much simpler.

Unfortunately it did not work for us.

We are not experiencing this problem so often on servers, only on clients (about 9 out of 12 client boxes).

On servers we use static IP:s on clients we use DHCP.
Changing a client to a static IP did fix the NFS upstart problem!!!
When we investigated that clue we turned a lot of stones (even replacing our
managed switches with dumb once) but we could not find a problem related
to DHCP in our setup.

Most of our clients are clones - therefore it is amazing that the problem is consistent
on one box and not on another.
If it is a timing problem related to how fast the hardware is it might make sense though.
(We have tried with flushing all DHCP leases records in order to rule out "unlucky" NIC)

On a private (MPD) server I have also had this problem,
In such cases, when there are services depending on NFS shares being mounted the
upstart script emits the event 'nfsshares-mounted',
This saves the day - allowing me to wait with starting these depending services.

Regards