Yes. I have noted systemd stops the network then tries to umount nfs on fedora 20. Not really a good plan. And I also did the rc.local mount as it was not mounting on boot because it tries to mount nfs before the network is live and fails. There do seem to be some significant issues around nfs and network start/stop timing. On Sun, Feb 22, 2015 at 8:14 AM, Tom Horsley <horsley1953@xxxxxxxxx> wrote: > On Sun, 22 Feb 2015 09:00:32 +0100 > Jens Neu wrote: > >> maybe since 2 weeks (close to upgrade to Twenty_One), my nfs shares are >> no longer mounted at boot. > > My consistent experience is that systemd has no clue when > the network is "up" if by up you mean actually capable of > talking to other things on the network. Thus all of the > dependencies it waits on never wait long enough. I moved > a slew of things to rc.local to have them restarted with > different delays between them and also run a script there > which keeps trying to mount all my NFS shares in a background > loop till they actually mount. Only with enough junk > in rc.local does my system boot reliably. > -- > users mailing list > users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
