Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ nfsd(8) — BSD/386 1.0

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

nfsstat(1)

nfssvc(2)

mountd(8)

portmap(8)

NFSD(8)                   BSD System Manager's Manual                  NFSD(8)

NAME
     nfsd - remote NFS server

SYNOPSIS
     nfsd [-r] [-t msk,mtch,hostadr1,hostadr2,...] [-u msk,mtch,numprocs]
          [numprocs]

DESCRIPTION
     Nfsd runs on a server machine to service NFS requests from client ma-
     chines.  At least one nfsd must be running for a machine to operate as a
     server.  The options -u and -t are used to indicate which transport pro-
     tocols are to be served.

     Options available to nfsd:

     -r      Register the NFS service with portmap(8) without creating any
             servers. This option can be used along with the -u or -t options
             to re-register NFS if the portmap server is restarted.

     -t      Serve TCP NFS clients.

     -u      Serve UDP NFS clients.

     The following arguments to the -u or -t options are used to specify pa-
     rameters for service using the respective protocol:

     msk, mtch
             These arguments permit restriction of NFS services to a subset of
             the host addresses. The msk and mtch are applied to the client
             host address as follows:

                   if (( hostaddress & msk ) == mtch )
                        - service the client request
                   else
                        - drop the request

     hostadr1, ...
             You may also specify zero or more specific host addresses to be
             accepted as well as ones that pass the msk, mtch test above.
             This may only be done for transport protocols that are connection
             based, such as TCP. For the internet domain, msk, mtch and
             hostadrs are specified in internet dot notation.

     numprocs
             Specifies how many servers to fork off. This may only be speci-
             fied for non-connection based protocols such as UDP.

     If neither -u or -t are specified, numprocs servers for UDP accepting re-
     quests from all clients are started.  If numprocs is not specified, it
     defaults to 1.

     For example:

     nfsd -u 255.255.255.0,131.104.48.0,4 -t \
             255.255.0.0,131.104.0.0,131.102.31.2

           Serves UDP and TCP transports. For UDP, it runs 4 daemons that ac-
           cept requests from any client on subnet 131.104.48.  For TCP, it
           accepts connections from any client on network 131.104 plus the
           client with the address 131.102.31.2.

     nfsd -u 255.255.240.0,131.104.0.0,6 -t 0,0


           Serves UDP and TCP transports.  For UDP, it runs 6 daemons that ac-
           cept requests from clients with addresses in the range 131.104.0.x
           - 131.104.15.x.  For TCP, it accepts connections from any client.

     nfsd -u 0,0,4

           Serves any UDP client with 4 servers, only.

     nfsd 4

           Serves any UDP client with 4 servers, only. (Compatibility)

     A server should typically run enough daemons to handle the maximum level
     of concurrency from its clients, typically four to six.

     Nfsd listens for service requests at the port indicated in the NFS server
     specification; see Network File System Protocol Specification, RFC1094.

SEE ALSO
     nfsstat(1),  nfssvc(2),  mountd(8),  portmap(8)

BUGS
     The client host address restrictions specified here are unrelated to the
     mount restrictions specified in /etc/exports for mountd(8).

HISTORY
     The nfsd command is currently under development.

BSDI BSD/386                    March 27, 1993                               2





































Typewritten Software • bear@typewritten.org • Edmonds, WA 98026