Am 24.12.2015 um 00:29 schrieb Bob Proulx: > Michael Biebl wrote: >> schrieb Bob Proulx: >>> If a client system requires an NFS mounted file system then the admin >>> must configure the network to be "auto" and not "allow-hotplug". >>> The simple reason is that because otherwise it won't work. :-) >> >> That's not quite acurate. The if-up.d hook scripts did work for >> allow-hotplug under sysvinit. It just meant, the NFS share was mounted >> at an arbitrary point during boot. >> So allow-hotplug and SysV init scripts with Required-Start: $network was >> not a good combination. > > I am talking about the traditional sysvinit system here. It needs > "auto" for it to work properly for NFS mounted file systems. > > For example a small corporate workstation which requires a hard > mounted NFS mounted (no autofs) $HOME for a user to be able to log > into the system.
allow-hotplug still works sufficiently under sysvinit. It will mount $HOME as soon as the network is up. It just doesn't block boot. So the worst thing that can happen is, that getty or gdm is already started even though $HOME has not been mounted yet. Under systemd, with allow-hotplug, having $HOME on NFS and the network is not yet up, you'll be dropped into rescue mode. That's a much worse error case then under sysvinit. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
