version 4, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
rpc.statd |
|
|
2 |
!!!rpc.statd |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
OPTIONS |
|
|
7 |
TCP_WRAPPERS SUPPORT |
|
|
8 |
FILES |
|
|
9 |
SEE ALSO |
|
|
10 |
AUTHORS |
|
|
11 |
---- |
|
|
12 |
!!NAME |
|
|
13 |
|
|
|
14 |
|
|
|
15 |
rpc.statd - NSM status monitor |
|
|
16 |
!!SYNOPSIS |
|
|
17 |
|
|
|
18 |
|
|
|
19 |
__/sbin/rpc.statd [[-F] [[-d] [[-?] [[-n name ] [[-o port ] [[-p |
|
|
20 |
port ] [[-V]__ |
|
|
21 |
!!DESCRIPTION |
|
|
22 |
|
|
|
23 |
|
|
|
24 |
The __rpc.statd__ server implements the NSM (Network |
|
|
25 |
Status Monitor) RPC protocol. This service is somewhat |
|
|
26 |
misnomed, since it doesn't actually provide active |
|
|
27 |
monitoring as one might suspect; instead, NSM implements a |
|
|
28 |
reboot notification service. It is used by the NFS file |
|
|
29 |
locking service, __rpc.lockd__, to implement lock |
|
|
30 |
recovery when the NFS server machine crashes and |
|
|
31 |
reboots. |
|
|
32 |
|
|
|
33 |
|
|
|
34 |
__Operation__ |
|
|
35 |
|
|
|
36 |
|
|
|
37 |
For each NFS client or server machine to be monitored, |
|
|
38 |
__rpc.statd__ creates a file in __/var/lib/nfs/sm__. |
|
|
39 |
When starting, it iterates through these files and notifies |
|
|
40 |
the peer __rpc.statd__ on those machines. |
|
|
41 |
!!OPTIONS |
|
|
42 |
|
|
|
43 |
|
|
|
44 |
__-F__ |
|
|
45 |
|
|
|
46 |
|
|
|
47 |
By default, __rpc.statd__ forks and puts itself in the |
|
|
48 |
background when started. The __-F__ argument tells it to |
|
|
49 |
remain in the foreground. This option is mainly for |
|
|
50 |
debugging purposes. |
|
|
51 |
|
|
|
52 |
|
|
|
53 |
__-d__ |
|
|
54 |
|
|
|
55 |
|
|
|
56 |
By default, __rpc.statd__ sends logging messages via |
|
|
57 |
syslog(3) to system log. The __-d__ argument |
|
|
58 |
forces it to log verbose output to __stderr__ instead. |
|
|
59 |
This option is mainly for debugging purposes, and may only |
|
|
60 |
be used in conjunction with the __-F__ |
|
|
61 |
parameter. |
|
|
62 |
|
|
|
63 |
|
|
|
64 |
__-n, --name__ ''name'' |
|
|
65 |
|
|
|
66 |
|
|
|
67 |
specify a name for __rpc.statd__ to use as the local |
|
|
68 |
hostname. By default, __rpc.statd__ will call |
|
|
69 |
gethostname(2) to get the local hostname. Specifying |
|
|
70 |
a local hostname may be useful for machines with more than |
|
|
71 |
one interfaces. |
|
|
72 |
|
|
|
73 |
|
|
|
74 |
__-o, --outgoing-port__ ''port'' |
|
|
75 |
|
|
|
76 |
|
|
|
77 |
specify a port for __rpc.statd__ to send outgoing status |
|
|
78 |
requests from. By default, __rpc.statd__ will ask |
|
|
79 |
portmap(8) to assign it a port number. As of this |
|
|
80 |
writing, there is not a standard port number that |
|
|
81 |
__portmap__ always or usually assigns. Specifying a port |
|
|
82 |
may be useful when implementing a firewall. |
|
|
83 |
|
|
|
84 |
|
|
|
85 |
__-p, --port__ ''port'' |
|
|
86 |
|
|
|
87 |
|
|
|
88 |
specify a port for __rpc.statd__ to listen on. By |
|
|
89 |
default, __rpc.statd__ will ask portmap(8) to |
|
|
90 |
assign it a port number. As of this writing, there is not a |
|
|
91 |
standard port number that __portmap__ always or usually |
|
|
92 |
assigns. Specifying a port may be useful when implementing a |
|
|
93 |
firewall. |
|
|
94 |
|
|
|
95 |
|
|
|
96 |
__-?__ |
|
|
97 |
|
|
|
98 |
|
|
|
99 |
Causes __rpc.statd__ to print out command-line help and |
|
|
100 |
exit. |
|
|
101 |
|
|
|
102 |
|
|
|
103 |
__-V__ |
|
|
104 |
|
|
|
105 |
|
|
|
106 |
Causes __rpc.statd__ to print out version information and |
|
|
107 |
exit. |
|
|
108 |
!!TCP_WRAPPERS SUPPORT |
|
|
109 |
|
|
|
110 |
|
|
|
111 |
This __rpc.statd__ version is protected by the |
|
|
112 |
__tcp_wrapper__ library. You have to give the clients |
|
|
113 |
access to __rpc.statd__ if they should be allowed to use |
|
|
114 |
it. To allow connects from clients of the .bar.com domain |
|
|
115 |
you could use the following line in |
|
|
116 |
/etc/hosts.allow: |
|
|
117 |
|
|
|
118 |
|
|
|
119 |
statd: .bar.com |
|
|
120 |
|
|
|
121 |
|
|
|
122 |
You have to use the daemon name __statd__ for the daemon |
|
|
123 |
name (even if the binary has a different name). |
|
|
124 |
|
|
|
125 |
|
|
|
126 |
For further information please have a look at the |
4 |
perry |
127 |
tcpd(8) and hosts_access(5) manual |
1 |
perry |
128 |
pages. |
|
|
129 |
!!FILES |
|
|
130 |
|
|
|
131 |
|
|
|
132 |
__/var/lib/nfs/state |
|
|
133 |
/var/lib/nfs/sm/* |
|
|
134 |
/var/lib/nfs/sm.bak/*__ |
|
|
135 |
!!SEE ALSO |
|
|
136 |
|
|
|
137 |
|
|
|
138 |
__rpc.nfsd(8), portmap(8)__ |
|
|
139 |
!!AUTHORS |
|
|
140 |
|
|
|
141 |
|
|
|
142 |
Jeff Uphoff |
|
|
143 |
Olaf Kirch |
|
|
144 |
H.J. Lu |
|
|
145 |
Lon Hohberger |
|
|
146 |
---- |