https://bugzilla.novell.com/show_bug.cgi?id=819515
https://bugzilla.novell.com/show_bug.cgi?id=819515#c3
--- Comment #3 from Scott Couston
If you have filesystems listed in /etc/fstab, then the correct thing for the boot process to do is to wait for all the filesystems to be available before continuing.
If you don't want that then you have 2 options. 1/ add the "bg" option to the NFS mounts in /etc/fstab. This will cause the mount to be attempted once with a fairly short timeout, and if that fails, to continue attempting in the back ground and let the system boot complete.
2/ use an automounter to have the NFS filesystem only mounted on demand. That way an unavailable NFS server will only block the applications that need it, not the whole system.
If you have hard mount requests for NFS filesystem in /etc/fstab, but expect the system to boot when the server is not available, then that is a configuration error.
I didn't really create this is a bug to help myself only. The issue is the default setting after using Yast>Network Services both >>NFS Server and Client are totally inadequate and create the illusion, to the user, the PC has frozen. If there are options let us put them in Yast GUI but as a default something has to change. If at time of boot the NFS Server and/or client is not available;sure wait a reasonable time like 6 seconds but dont stall the whole boot process of a PC to the point users think that their PC has frozen. The issue of NFS v4 or not using is is not clear in help. The option to use GSS Security is totally unclear. With respect to services being activating and being run as PART of the kernel with respect to NFS drives; I didn't make clear. I dont understand why, with Network Drives (mount points) that the kernel cannot monitor ALL Network mount points and exported services! If any become available after boot; or unavailable, the kernel should auto mount or auto dismount as a dynamic property. We shouldn't need services to be running to accomplish. To solve this reoccurring problem, can we just have a default that mounts if its there or waits 6 or so seconds and if not there continue the boot process - Its as simple as that! When we work out what to do with Yast in the future we can add the options in the GUI...Users just want it to work. Admins expect Yast GUI to offer clear choices and all options and simple WORK - NOTHING MORE.. WE can no longer sit between editing files and have GUI's that accomplish everything an admin wants to do...Hate it or not; but the GUI just simply has to work! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.