Technical data

NFS Client
21.4 Mounting Files and Directories
4. TCPIP> MOUNT DNFS1:[B] /HOST=MARGE /PATH="DKA0/TEST"
Mount count: 3 (system mount, not incremented)
5. TCPIP> DISMOUNT DNFS1:[A]
Mount count: 2
6. $ DISMOUNT DNFS1:
Mount count: 1 (removed mount in example 3, decremented)
7. $ DISMOUNT DNFS1:
Mount count: 0 (removed mount in example 4, decremented)
The original mount for BART "/ENG" on DNFS1:[A], along with its shared mount,
is dismounted. The subsequent DISMOUNT commands dismount examples 3 and
4, leaving nothing mounted.
21.4.2 Automounting
Automounting allows you to mount a remote file system on an as-needed basis.
This means that the client automatically and transparently mounts a remote
server path as soon as the user accesses the path name.
Automounting is convenient for file systems that are inactive for large periods
of time. When a user on a system invokes a command to access a remote file or
directory, the automount daemon mounts the file and keeps it mounted as long as
the user needs it. When a specified amount of time elapses without the file being
accessed, it is dismounted. You can specify an inactivity period (5 minutes is the
default), after which the software automatically dismounts the path.
You specify automounting and an inactivity interval with the qualifier
/AUTOMOUNT=INACTIVITY:OpenVMS_delta_time.
The inactivity interval is the maximum inactive period for the mount attempt.
When this period expires, the NFS client dismounts the path name as described
below.
In this example, the client automounts directory
/usr/webster residing on host
robin onto the OpenVMS mount point DNFS67:. When it references the path
name, the client keeps the path mounted unless it reaches an inactive period of
10 minutes, after which it dismounts the file system. With subsequent references,
the client remounts the file system. For example:
TCPIP> MOUNT DNFS67: /HOST="robin" -
_TCPIP> /PATH="/usr/webster" /AUTOMOUNT=INACTIVITY=00:10:00
21.4.3 Background Mounting
Background mounting allows you to retry a file system mount that initially
failed. For example, you may have set mount points in your system startup
command file so they are automatically mounted every time your system reboots.
In this scenario, if the server is unavailable (because, for example, the server is
also rebooting), the mount requests fail. With background option set, the client
continues to try the mount after the initial failure. The client continues trying
up to 10 times at 30-second intervals (default) or for the number of retries and
interval you specify.
21–10 NFS Client