# mountsrv
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
mountsrv is a shell alias to mount 4 noauto nfs mounts that I have used in fstabs
since around when nfs V4 went mainstream. Nothing in fstab has been changed WRT
nfs mounts. The only changes to fstab are: 1-because of cloning 36 so that the
clone could be upgraded to 37 while keeping 36 intact, with only change being
related to the / filesystem's new device name, UUID and LABEL post-cloning; and
2-an extra mount during system-upgrade process, for a filesystem mounted to
/var/lib/dnf/system-upgrade to prevent exhaustion of freespace by downloading all
before installing any.
Running systemctl daemon-reload doesn't change anything apparent, or stop the
"hints" from recurring after each reboot. Is this a bug? BZ search for
"daemon-reload" turned up nothing looking similar. Is there some required new
fstab construct I haven't heard about?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata