nfsd(1m) - osol9

1nfsd(1M)                System Administration Commands                nfsd(1M)
2
3
4

NAME

6       nfsd - NFS daemon
7

SYNOPSIS

9       /usr/lib/nfs/nfsd [-a] [-c #_conn] [-l listen_backlog]
10            [-p protocol] [-t device] [nservers]
11
12

DESCRIPTION

14       nfsd is the daemon that handles client file system requests. Only users
15       with {PRIV_SYS_NFS} and sufficient privileges to write to /var/run  can
16       run this daemon.
17
18
19       The  nfsd  daemon  is automatically invoked using share(1M) with the -a
20       option.
21
22
23       By default, nfsd starts over the TCP and UDP transports for versions  2
24       and 3. By default, it starts over the TCP for version 4. You can change
25       this with the -p option.
26
27
28       A previously invoked nfsd daemon started with or without  options  must
29       be stopped before invoking another nfsd command.
30
31
32       To  change  startup  parameters  for  nfsd,  use  the  sharectl(1M) and
33       sharemgr(1M) commands.
34

OPTIONS

36       The following options are supported:
37
38       -a             Start a NFS daemon over all available connectionless and
39                      connection-oriented  transports,  including UDP and TCP.
40                      Equivalent of setting the NFSD_PROTOCOL parameter to ALL
41                      in the nfs file.
42
43
44       -c #_conn      This  sets  the maximum number of connections allowed to
45                      the NFS server over connection-oriented  transports.  By
46                      default, the number of connections is unlimited. Equiva‐
47                      lent of the NFSD_MAX_CONNECTIONS parameter  in  the  nfs
48                      file.
49
50
51       -l             Set  connection queue length for the NFS TCP over a con‐
52                      nection-oriented transport.  The  default  value  is  32
53                      entries. Equivalent of the NFSD_LISTEN_BACKLOG parameter
54                      in the nfs file.
55
56
57       -p protocol    Start a NFS daemon over the specified protocol.  Equiva‐
58                      lent of the NFSD_PROTOCOL parameter in the nfs file.
59
60
61       -t device      Start  a  NFS  daemon for the transport specified by the
62                      given device. Equivalent of the NFSD_DEVICE parameter in
63                      the nfs file.
64
65

OPERANDS

67       The following operands are supported:
68
69       nservers    This  sets  the  maximum  number of concurrent NFS requests
70                   that the server can handle. This concurrency is achieved by
71                   up  to  nservers  threads  created as needed in the kernel.
72                   nservers should be based  on  the  load  expected  on  this
73                   server.  16 is the usual number of nservers. If nservers is
74                   not  specified,  the  maximum  number  of  concurrent   NFS
75                   requests  will default to 1. Equivalent of the NFSD_SERVERS
76                   parameter in the nfs file.
77
78

USAGE

80       If the NFS_PORTMON variable is set in  /etc/system,  then  clients  are
81       required  to  use privileged ports (ports < IPPORT_RESERVED) to get NFS
82       services. This variable is equal to zero by default. This variable  has
83       been  moved  from  the  "nfs" module to the "nfssrv" module. To set the
84       variable, edit the /etc/system file and add this entry:
85
86
87       set nfssrv:nfs_portmon = 1
88

EXIT STATUS

90       0    Daemon started successfully.
91
92
93       1    Daemon failed to start.
94
95

FILES

97       .nfsXXX                 Client machine pointer to an  open-but-unlinked
98                               file.
99
100
101       /etc/default/nfs        Contains startup parameters for nfsd.
102
103
104       /etc/system             System configuration information file.
105
106
107       /var/nfs/v4_state       Directories used by the server to manage client
108       /var/nfs/v4_oldstate    state information. These directories should not
109                               be removed.
110
111

ATTRIBUTES

113       See attributes(5) for descriptions of the following attributes:
114
115
116
117
118       ┌─────────────────────────────┬─────────────────────────────┐
119       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
120       ├─────────────────────────────┼─────────────────────────────┤
121       │Availability                 │SUNWnfssu                    │
122       └─────────────────────────────┴─────────────────────────────┘
123

NOTES

132       Manually starting and restarting nfsd is not recommended. If it is nec‐
133       essary  to  do  so,  use  svcadm  to  enable or disable the nfs service
134       (svc:/network/nfs/server). If it is disabled, it  will  be  enabled  by
135       share_nfs(1M),  unless  its  application/auto_enable property is set to
136       false. See the , and svcadm(1M) for more information.
137
138
139       The nfsd service is managed by the service management facility, smf(5),
140       under the service identifier:
141
142         svc:/network/nfs/server
143
144
145
146
147       Administrative actions on this service, such as enabling, disabling, or
148       requesting restart, can be performed using  svcadm(1M).  The  service's
149       status can be queried using the svcs(1) command.
150
151
152       If nfsd is killed with SIGTERM, it will not be restarted by the service
153       management facility. Instead, nfsd can be restarted by  other  signals,
154       such as SIGINT.
155
156
157
158SunOS 5.11                        22 Jul 2008                         nfsd(1M)