On Thu, 2011-12-15 at 15:09 +0100, Ruediger Meier wrote:
On Thursday 15 December 2011, Anton Aylward wrote:
Christoph Bartoschek said the following on 12/15/2011 07:51 AM:
t is quite embarassing but I have found my problem. Starting with 11.4 the nfs service is not starting automatically. One has to enable it for runlevels 3,5 to get automatically mounted remote filesystems.
I wonder why I thought that this problem started with 12.1. I think the few 11.4 machines we have were not rebooted after initial setup so the problem did not appear.
To sum up: for opensuse systemd is not responsible for mounting remote filesystems. It is the nfs service.
Enabling the service solves the problem. However it does not solve the hang with comment=systemd.automount. So I had to remove the comment.
I'm sorry, this makes no sense to me.
NFS doesn't mount the file systems.
You mount them in the automounter or the fstab with 11.4 or with explicit units or the fstab with SystemD
There should be no need to use automounter to mount NFS dirs. After knowing Christoph's real problem we see that this is still true even using systemd.
My only need for automounter is when the client and server boot at the same time. If NFS is set to not block when mounting (via an entry in /etc/fstab), when the server is not ready when the client tries, the non-blocking mount will, as expected, not block - or mount. And the mount will never happen again. If it is an automount, there is the added delay in the client of the user needing to log in (assuming the mount is a user-related mount). -- Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org