On Sat, 18 Jan 2014 18:53:37 +0800 Ian Chapman <packages@xxxxxxxxxxxxxxxxxx> wrote: > On 18/01/14 17:34, Ed Greshko wrote: > > I suppose this is more of an FYI until I can determine where the > > bugzilla goes..... > > > > If you use a "hostname" in your fstab for nfs mounts and your > > system is running bind and the resolv.conf is set to 127.0.0.1 the > > nfs mounts will fail at boot time. This is true even if you have > > NetworkManager-wait-online enabled and an entry for the host in the > > hosts file. > > > > Examining the journal shows that the mount attempt happens prior to > > named getting started, obviously. :-) > > > > Sort of leaning towards a systemd bugzilla > > Does NetworkManager-wait-online actually still work in F19+? I have > similar issues with autofs (ie IPA not available when autofs starts) > and setting this in F18 and earlier solved the problem. Makes no > difference in F19+. > > Would having nm.service start earlier help? Maybe a custom file? ------------------------------------- .include /usr/lib/systemd/system/NetworkManager.service [Unit] Before=nfs whatever # I don't use nfs currently, save as /etc/systemd/system/NetworkManager.service ___ Regards, Frank www.frankly3d.com -- 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
