I've had for a long time a setup for (Fedora-)laptops where the laptop has local home directories for users in /home/<username> and in fstab the directory is mounted (when available) to NFS share on home network.
This worked nicely until recently (F28/F29) when it seems that automount was configured to attempt to mount /home as the user logs on (GDM). Since this automount fails, the login is terminated despite the fact that there is a valid /home/<username> on the fs.
So the question is: Is there anything similar in simplicity to set up as a replacement to the current setup, or, alternatively, how does one disable the automount from attempting to mount non-reachable NFS mounts at login time?
Poltsi
On Mon, 11 Feb 2019 at 04:46, Paul-Erik Törrönen poltsi@poltsi.fi wrote:
I've had for a long time a setup for (Fedora-)laptops where the laptop has local home directories for users in /home/<username> and in fstab the directory is mounted (when available) to NFS share on home network.
This worked nicely until recently (F28/F29) when it seems that automount was configured to attempt to mount /home as the user logs on (GDM). Since this automount fails, the login is terminated despite the fact that there is a valid /home/<username> on the fs.
So the question is: Is there anything similar in simplicity to set up as a replacement to the current setup, or, alternatively, how does one disable the automount from attempting to mount non-reachable NFS mounts at login time?
This change might be the new systemd automounter. If your previous configuration was using autofs, that should still be available. More detail would be helpful.
On 2019-02-11 14:45, George N. White III wrote:
This change might be the new systemd automounter. If your previous configuration was using autofs, that should still be available. More detail would be helpful.
My setup was simple, I had the following line in /etc/fstab:
nfs-server:/path/to/home /home nfs defaults 0 0
Locally on the laptop there is also /home/<user> (with the correct uid and gid).
When the laptop is not connected to the local network (ie. the nfs-server is not available), the user logs on using the local version of /home/<user>. When the laptop is connected to the local network (ie. the nfs-server is available), the laptop mounts nfs-server:/path/to/home to /home at boot time and the user logs on using the nfs-server version of /home (which has matching uid/gid on files and directories).
Does this clarify the case?
Poltsi
On 2/11/19 6:30 AM, Paul-Erik Törrönen wrote:
My setup was simple, I had the following line in /etc/fstab:
nfs-server:/path/to/home /home nfs defaults 0 0
That's not "automount." That's just a normal NFS filesystem. Using the word "automount" will confuse people about what you're trying to do.
Replace the word "defaults" with the word "nofail" and the system should behave like it used to.
On 2019-02-11 18:21, Gordon Messmer wrote:
On 2/11/19 6:30 AM, Paul-Erik Törrönen wrote:
My setup was simple, I had the following line in /etc/fstab:
nfs-server:/path/to/home /home nfs defaults 0 0
That's not "automount." That's just a normal NFS filesystem. Using the word "automount" will confuse people about what you're trying to do.
You misunderstood me. With the latest updatest to F28/29 it is automount which is "breaking" my system of plain old NFS setup that I had.
To reiterate: Currently a user can not log on to a laptop which has the fstab-line described above when the laptop is not connected to the local network.
In the logs I can see that this is because during the login process automount now tries to mount the NFS share and fails. This happens despite the fact that there is a valid /home/<user> directory (a local copy).
Replace the word "defaults" with the word "nofail" and the system should behave like it used to.
Thanks, will try this.
Poltsi
-
George N. White III -
Gordon Messmer -
Paul-Erik Törrönen