fs-nfs2

NFS 2 client filesystem (QNX Neutrino)

---

You must be root to start this manager.

---

Syntax:

fs-nfs2 [-b num] [-B size] [-D] [-e] [-h] 
        [-i nodes] [-r] [-S] [-t] [-u] [-v[v]...] 
        [-Z n] [server:export] [mountpoint]
        [[-erStu] [-Z n] server:export mountpoint ...]

Runs on:

Neutrino

Options:

server

The name of the NFS server.

export

The directory to be exported from the server.

mountpoint

The name under which the exported directory is to be mounted.

The following options apply to all mountpoints:

-b num

Use num buffers (default: 200).

-B size

Set the buffer size to size bytes. The default is set by the first server, and is usually 8K.

-D

Run in the foreground.

-h

Display usage information.

-i nodes

Set the number of inodes to nodes.

-v[v]...

Verbose output; add more v characters for more verbosity. In order to capture the log messages, you need to have syslogd running.

The following options apply only to the next mountpoint specified on the command line:

-e

Set the NO EXEC flag for the mounted filesystem.

-r

Set the READ ONLY flag for the mounted filesystem.

-S

Don't cache symlinks.

-t

Use TCP instead of UDP. If this fails, fs-nfs2 uses UDP.

-u

Use UDP (which is the default). If this fails, fs-nfs2 fails.

-Z n

The value of n indicates how to attach to the path:

• B or b — attach before other managers.
• A or a — attach after other managers.
• O or o — make the attachment opaque; don't resolve to mountpoints with shorter pathname matches. The pathname resolver tries to find the longest match against all pathnames attached.

The default is none of these. For more information, see “Ordering mountpoints” in the Process Manager chapter of the System Architecture guide.

Description:

The fs-nfs2 filesystem manager is an NFS 2 client operating over TCP/IP. To use it, you must have an NFS server.

This filesystem manager requires a TCP/IP transport layer, such as the one provided by io-pkt*. It also needs socket.so and libc.so.

By default, this utility does not set any upper limit for number of inodes.

You can also create mountpoints with the mount command by specifying nfs for the type. You must start fs-nfs2 before creating mountpoints in this manner. If you start fs-nfs2 without any arguments, it runs in the background so you can use mount.

Examples:

Mount the qnx_bin export as /bin from an NFS server named server_node:

fs-nfs2 server_node:/qnx_bin /bin &

Mount /nfs1 using TCP, and /nfs2 using UDP:

fs-nfs2 -t host1:/ /nfs1 host2:/ /nfs2

Mount both using TCP:

fs-nfs2 -t host1:/ /nfs1 -t host2:/ /nfs2

Caveats:

If possible, you should use fs-nfs3 instead of fs-nfs2.

See also:

fs-cifs, fs-nfs3, io-pkt*, mount, syslogd, umount

Filesystems chapter of System Architecture

QNX Neutrino User's Guide:

• “NFS filesystem” in the Working With Filesystems chapter
• “Filesystem limits” in the Understanding System Limits chapter