NFS 2 client filesystem (QNX Neutrino)
|You must be root to start this manager.|
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 ...]
The following options apply to all mountpoints:
The following options apply only to the next mountpoint specified on the command line:
The default is none of these. For more information, see "Ordering mountpoints" in the Process Manager chapter of the System Architecture guide.
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-net with the npm-tcpip.so. 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.
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
If possible, you should use fs-nfs3 instead of fs-nfs2.
fs-cifs, fs-nfs3, io-net, mount, npm-tcpip.so, npm-ttcpip.so, syslogd, umount
"NFS filesystem" in the Working With Filesystems chapter of the User's Guide