On Fri, 27 May 2011 08:52:50 -0400 Dr. Michael J. Chudobiak wrote: > Maybe, but I don't understand why it takes ~30 seconds to establish a > NFSv4 mount. What's the root problem here? Well, the root problem is NFS :-). I don't understand any of what is going on with systemd and network mounts. I don't timeout, my network mounts simply fail right away: https://bugzilla.redhat.com/show_bug.cgi?id=692008 (I think that's the bug I'm seeing). Anyway, I just wrote a couple of shell scripts. One finds all the NFS mountpoints not marked noauto in the /etc/fstab, then it invokes the other script in the background, passing it the name of the mountpoint. The other script loops calling mount every few seconds as long as the mounts keeps failing, then when the filesystem is finally mounted it exits. I start the first script from rc.local, and now I have reliable network mounts that don't delay the boot (I've always wanted an option that would background the mount right away without timing out once first, now I kind of have one). Systemd isn't the only system that fails to mount network files. I have the same problems with upstart on ubuntu virtual machines as well and have to fix it much the same way. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
