The Linux Administration group is for the discussion of technical issues technical issues that arise during the administration of Linux systems, including maintaining the operating system and supporting end-user applications.

Earlier releases use the portmap tool instead.
Starting NFS services after each boot

Linux uses the concept of runlevels to manage which services can run concurrently. There are normally seven runlevels, numbered 0 to 6. For example, a system shutdown corresponds to runlevel 0, where all services should be stopped.

When a Linux system boots, it runs in the runlevel defined as the default runlevel. For most distributions, this is either 3,4 or 5

To check the runlevels at which the NFS services are automatically started or stopped, run the following commands:

Actually any script beginning with a "K" is the "kill" version for
shutting down the service (although it's basically a flag, not
fundamentally different from the "S" script that starts the service).
So you probably still want a "K" version in whichever directory you
found it.

(In other words, here you'd want to cp the "K" file to your "S" one,
not mv it. Also be aware that in some UNIX/Linux variants the "K"
script can be listed in more than one "rc" directory.)

There's nothing necessarily wrong with changing the order of when the
"S" script is invoked, provided no other startup dependencies for the
service being delayed are between the old number and the new one.

_netdev:
The _netdev option tells the system to wait until the network is up before
trying to mount the share. Systemd assumes this for NFS, but anyway it is
good practice to use it for all types of networked file systems

Another method is using the systemd automount service. This is a better
option than _netdev, because it remounts the network device quickly when
the connection is broken and restored. As well, it solves the problem from
autofs

Hi,
Exactly that is the problem. File systems are mounted before network is
up, so here os tries to mount the nfs but fails because there is no
network. While booting if you follow the details you would be able to see
the steps and failing message.

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.