4 .\" Copyright (C) 1999 Olaf Kirch <okir@monad.swb.de>
5 .\" Modified by Jeffrey A. Uphoff, 1999, 2002.
6 .\" Modified by Lon Hohberger, 2000.
7 .\" Modified by Paul Clements, 2004.
9 .\" Japanese Version Copyright (c) 2002 NAKANO Takeo all rights reserved.
10 .\" Translated Sun 29 Sep 2002 by NAKANO Takeo <nakano@apm.seikei.ac.jp>
11 .\" Updated & Modified Wed 29 Mar 2006 by Yuichi SATO <ysato444@yahoo.co.jp>
13 .TH rpc.statd 8 "31 Aug 2004"
15 .\"O rpc.statd \- NSM status monitor
17 rpc.statd \- NSM ¥¹¥Æ¡¼¥¿¥¹¥â¥Ë¥¿
20 .B "/sbin/rpc.statd [-F] [-d] [-?] [-n " name "] [-o " port "] [-p " port "] [-H " prog "] [-V]"
25 .\"O server implements the NSM (Network Status Monitor) RPC protocol.
26 .\"O This service is somewhat misnomed, since it doesn't actually provide
27 .\"O active monitoring as one might suspect; instead, NSM implements a
28 .\"O reboot notification service. It is used by the NFS file locking service,
30 .\"O to implement lock recovery when the NFS server machine crashes and
32 .\"nakano misnomed ¤Ï misnamed ¤«¤Ê
34 ¥µ¡¼¥Ð¤Ï NSM (Network Status Monitor) RPC ¥×¥í¥È¥³¥ë¤ò¼ÂÁõ¤·¤¿¤â¤Î¤Ç¤¢¤ë¡£
35 ¤³¤Î¥µ¡¼¥Ó¥¹¤Ï¾¯¡¹Ì¾Á°¤¬Å¬ÀڤǤϤʤ¯¡¢
36 ͽÁÛ¤µ¤ì¤ë¤è¤¦¤Ê¥¢¥¯¥Æ¥£¥Ö¤Ê¥â¥Ë¥¿¥ê¥ó¥°¤ò¼ÂºÝ¤Ë¹Ô¤¦¤ï¤±¤Ç¤Ï¤Ê¤¤¡£
37 ¼ÂºÝ¤Ë¤Ï NSM ¤Ï¥ê¥Ö¡¼¥ÈÄÌÃÎ¥µ¡¼¥Ó¥¹¤ò¼ÂÁõ¤·¤¿¤â¤Î¤Ê¤Î¤Ç¤¢¤ë¡£
39 ¤Ï NFS ¥Õ¥¡¥¤¥ë¥í¥Ã¥¯¥µ¡¼¥Ó¥¹
42 NFS ¥µ¡¼¥Ð¥Þ¥·¥ó¤¬¥¯¥é¥Ã¥·¥å¤·¤ÆÉüµ¢¤·¤¿¤È¤¤Ë¡¢
43 ¥í¥Ã¥¯¤ò²óÉü¤¹¤ë¤¿¤á¤ËÍѤ¤¤é¤ì¤ë¡£
46 .\"O For each NFS client or server machine to be monitored,
48 .\"O creates a file in
49 .\"O .BR /var/lib/nfs/sm .
50 .\"O When starting, it iterates through these files and notifies the
53 .\"O on those machines.
55 NFS ¤Î¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð¤Î¥Þ¥·¥ó¤½¤ì¤¾¤ì¤ËÂФ·¡¢
62 ¤Ï¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤ò½ç¼¡Ä´¤Ù¡¢
63 ¤½¤ì¤éÀܳÀè¤Î¥Þ¥·¥ó¤Î
72 .\"O forks and puts itself in the background when started. The
74 .\"O argument tells it to remain in the foreground. This option is
75 .\"O mainly for debugging purposes.
78 ¤Ï¥Õ¥©¡¼¥¯¤·¤Æ¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Ë°ÜÆ°¤·¤Æ¤«¤éÆ°ºî¤ò»Ï¤á¤ë¡£
82 ¤Ë¥Õ¥©¥¢¥°¥é¥¦¥ó¥É¤Ëα¤Þ¤ë¤è¤¦ÅÁ¤¨¤ë¡£
83 ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¼ç¤Ë¥Ç¥Ð¥Ã¥°¤Î¤¿¤á¤Î¤â¤Î¤Ç¤¢¤ë¡£
88 .\"O sends logging messages via
90 .\"O to system log. The
92 .\"O argument forces it to log verbose output to
94 .\"O instead. This option is mainly for debugging purposes, and may only
95 .\"O be used in conjunction with the
102 ¤òÄ̤·¤Æ¥·¥¹¥Æ¥à¥í¥°¤ËÁ÷¤ë¡£
104 ¥ª¥×¥·¥ç¥ó¤Ï¡¢¤³¤Î¥í¥°½ÐÎϤò¾ÜºÙ¤Ë¤·¡¢
107 ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¼ç¤Ë¥Ç¥Ð¥Ã¥°¤Î¤¿¤á¤Î¤â¤Î¤Ç¤¢¤ê¡¢
110 ¤ÈƱ»þ¤Ë¤Î¤ß»È¤¦¤³¤È¤Ë¤Ê¤ë¤À¤í¤¦¡£
112 .BI "\-n," "" " \-\-name " name
113 .\"O specify a name for
115 .\"O to use as the local hostname. By default,
118 .\"O .BR gethostname (2)
119 .\"O to get the local hostname. Specifying
120 .\"O a local hostname may be useful for machines with more than one
123 ¤¬¥í¡¼¥«¥ë¤Î¥Û¥¹¥È̾¤È¤·¤ÆÍѤ¤¤ë̾Á°¤ò»ØÄꤹ¤ë¡£
128 ¤ò¸Æ¤ó¤Ç¥í¡¼¥«¥ë¤Î¥Û¥¹¥È̾¤ò¼èÆÀ¤¹¤ë¡£
129 ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤¬ 2 ¤Ä°Ê¾å¤¢¤ë¥Þ¥·¥ó¤Ç¤Ï¡¢
130 ¥í¡¼¥«¥ë¤Î¥Û¥¹¥È̾¤ò»ØÄꤹ¤ë¤ÈÊØÍø¤«¤â¤·¤ì¤Ê¤¤¡£
132 .BI "\-o," "" " \-\-outgoing\-port " port
133 .\"O specify a port for
135 .\"O to send outgoing status requests from. By default,
139 .\"O to assign it a port number. As of this writing, there is not
140 .\"O a standard port number that
142 .\"O always or usually assigns. Specifying
143 .\"O a port may be useful when implementing a firewall.
145 ¤¬³°¸þ¤¤Î¥¹¥Æ¡¼¥¿¥¹¥ê¥¯¥¨¥¹¥È¤òÁ÷¿®¤¹¤ë¤È¤¤Ë»È¤¦¥Ý¡¼¥È¤ò»ØÄꤹ¤ë¡£
150 ¤Ë¥Ý¡¼¥ÈÈÖ¹æ¤ò³ä¤êÅö¤Æ¤Æ¤¯¤ì¤ë¤è¤¦Í׵᤹¤ë¡£
151 ¤³¤Î¥Þ¥Ë¥å¥¢¥ë¤Î¼¹É®»þÅÀ¤Ç¤Ï¡¢
153 ¤¬¾ï¤Ë³ä¤êÅö¤Æ¤ËÍѤ¤¤ë¤è¤¦¤Ê¡¢É¸½àŪ¤Ê¥Ý¡¼¥ÈÈÖ¹æ¤Ï¤Ê¤¤¡£
154 ¥Ý¡¼¥È¤Î»ØÄê¤Ï¡¢¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤ò¼ÂÁõ¤¹¤ë¤È¤¤ËÊØÍø¤À¤í¤¦¡£
156 .BI "\-p," "" " \-\-port " port
157 .\"O specify a port for
159 .\"O to listen on. By default,
163 .\"O to assign it a port number. As of this writing, there is not
164 .\"O a standard port number that
166 .\"O always or usually assigns. Specifying
167 .\"O a port may be useful when implementing a firewall.
169 ¤¬ listen ¤¹¤ë¥Ý¡¼¥È¤ò»ØÄꤹ¤ë¡£
174 ¤Ë¥Ý¡¼¥ÈÈÖ¹æ¤ò³ä¤êÅö¤Æ¤Æ¤¯¤ì¤ë¤è¤¦Í׵᤹¤ë¡£
175 ¤³¤Î¥Þ¥Ë¥å¥¢¥ë¤Î¼¹É®»þÅÀ¤Ç¤Ï¡¢
177 ¤¬¾ï¤Ë³ä¤êÅö¤Æ¤ËÍѤ¤¤ë¤è¤¦¤Ê¡¢É¸½àŪ¤Ê¥Ý¡¼¥ÈÈÖ¹æ¤Ï¤Ê¤¤¡£
178 ¥Ý¡¼¥È¤Î»ØÄê¤Ï¡¢¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤ò¼ÂÁõ¤¹¤ë¤È¤¤ËÊØÍø¤À¤í¤¦¡£
180 .BI "\-P," "" " \-\-state\-directory\-path " directory
181 .\"O specify a directory in which to place statd state information.
182 .\"O If this option is not specified the default of
183 .\"O .BR /var/lib/nfs
185 statd ¤Î¾õÂÖ¾ðÊó¤òÃÖ¤¯¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤹ¤ë¡£
186 ¤³¤Î¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤Ê¤¤¾ì¹ç¡¢¥Ç¥Õ¥©¥ë¥È¤Î
191 .\"O Causes statd to run in the notify-only mode. When started in this mode, the
192 .\"O statd program will check its state directory, send notifications to any
193 .\"O monitored nodes, and exit once the notifications have been sent. This mode is
194 .\"O used to enable Highly Available NFS implementations (i.e. HA-NFS).
195 statd ¤òÄÌÃÎÀìÍѥ⡼¥É¤Ç¼Â¹Ô¤µ¤»¤ë¡£
196 ¤³¤Î¥â¡¼¥É¤Çµ¯Æ°¤¹¤ë¤È¡¢
197 statd ¥×¥í¥°¥é¥à¤Ï¾õÂÖ¾ðÊó¤òÃÖ¤¯¥Ç¥£¥ì¥¯¥È¥ê¤ò¥Á¥§¥Ã¥¯¤·¤Æ¡¢
198 Á´¤Æ¤Î¥â¥Ë¥¿ÂоݥΡ¼¥É¤ËÄÌÃΤòÁ÷¿®¤·¡¢ÄÌÃΤÎÁ÷¿®¤¬´°Î»¤·¤¿¤é½ªÎ»¤¹¤ë¡£
199 ¤³¤Î¥â¡¼¥É¤Ï¹â²ÄÍÑÀ (Highly Available) NFS ¼ÂÁõ (¤Ä¤Þ¤ê HA-NFS) ¤ò
200 ͸ú¤Ë¤¹¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤ë¡£
202 .BI "\-H, " "" " \-\-ha-callout " prog
203 .\"O Specify a high availability callout program, which will receive callouts
204 .\"O for all client monitor and unmonitor requests. This allows
206 .\"O to be used in a High Availability NFS (HA-NFS) environment. The
207 .\"O program will be run with 3 arguments: The first is either
211 .\"O depending on the reason for the callout.
212 ¹â²ÄÍÑÀ¥³¡¼¥ë¥¢¥¦¥È¥×¥í¥°¥é¥à¤ò»ØÄꤹ¤ë¡£
213 ¤³¤Î¥×¥í¥°¥é¥à¤ÏÁ´¤Æ¤Î¥¯¥é¥¤¥¢¥ó¥È¥â¥Ë¥¿¤È¥â¥Ë¥¿½ªÎ»¥ê¥¯¥¨¥¹¥È¤ËÂФ¹¤ë
214 ¥³¡¼¥ë¥¢¥¦¥È¤ò¼õ¤±¼è¤ë¡£
217 ¤ò¹â²ÄÍÑÀ NFS (HA-NFS) ´Ä¶¤Ç»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤¤ë¡£
218 ¤³¤Î¥×¥í¥°¥é¥à¤Ï 3 ¤Ä¤Î°ú¤¿ô¤òÉÕ¤±¤Æ¼Â¹Ô¤µ¤ì¤ë¡£
223 ¤Ç¤¢¤ê¡¢¥³¡¼¥ë¥¢¥¦¥È¤ÎÍýͳ¤Ë°Í¸¤¹¤ë¡£
224 .\"O The second will be the name of the client.
225 2 ¤ÄÌܤϥ¯¥é¥¤¥¢¥ó¥È¤Î̾Á°¤Ç¤¢¤ë¡£
226 .\"O The third will be the name of the server as known to the client.
227 3 ¤ÄÌܤϥ¯¥é¥¤¥¢¥ó¥È¤ËÃΤ餻¤ë¥µ¡¼¥Ð¤Î̾Á°¤Ç¤¢¤ë¡£
232 .\"O to print out command-line help and exit.
233 ¥³¥Þ¥ó¥É¥é¥¤¥ó¥Ø¥ë¥×¤òɽ¼¨¤·¤Æ½ªÎ»¤¹¤ë¡£
238 .\"O to print out version information and exit.
239 ¥Ð¡¼¥¸¥ç¥ó¾ðÊó¤òɽ¼¨¤·¤Æ½ªÎ»¤¹¤ë¡£
243 .\"O .SH TCP_WRAPPERS SUPPORT
244 .SH TCP_WRAPPERS ¤Î¥µ¥Ý¡¼¥È
247 .\"O version is protected by the
249 .\"O library. You have to give the clients access to
251 .\"O if they should be allowed to use it. To allow connects from clients of
252 .\"O the .bar.com domain you could use the following line in /etc/hosts.allow:
257 ¥é¥¤¥Ö¥é¥ê¤Ë¤è¤Ã¤ÆÊݸ¤ì¤Æ¤¤¤ë¡£
260 ¤ËÂФ¹¤ë¥¢¥¯¥»¥¹¤¬É¬Íפʤ顢
261 µö²Ä¤¹¤ë¤è¤¦ÀßÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£.bar.com ¥É¥á¥¤¥ó¤Î
262 ¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë¤Ë¤Ï¡¢
263 /etc/hosts.allow ¤Ë¼¡¤Î¤è¤¦¤Ë½ñ¤±¤Ð¤è¤¤¡£
269 .\"O You have to use the daemon name
271 .\"O for the daemon name (even if the binary has a different name).
272 ¥Ç¡¼¥â¥ó¤Î̾Á°¤Ï (¥Ð¥¤¥Ê¥ê¤Î¥Õ¥¡¥¤¥ë̾¤¬°Û¤Ê¤Ã¤Æ¤¤¤Æ¤â)
274 ¤È¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
276 .\"O For further information please have a look at the
279 .\"O .BR hosts_access (5)
292 .\"O to re-read the notify list from disk
293 .\"O and send notifications to clients. This can be used in High Availability NFS
294 .\"O (HA-NFS) environments to notify clients to reacquire file locks upon takeover
295 .\"O of an NFS export from another server.
299 ¤Ï¥Ç¥£¥¹¥¯¤«¤éÄÌÃΥꥹ¥È¤òÆɤßľ¤·¤Æ¡¢¥¯¥é¥¤¥¢¥ó¥È¤ËÄÌÃΤòÁ÷¤ë¡£
300 ¤³¤Î¥·¥°¥Ê¥ë¤Ï¹â²ÄÍÑÀ NFS (HA-NFS) ´Ä¶¤Ë¤ª¤¤¤Æ¡¢
301 ¾¤Î¥µ¡¼¥Ð¤«¤é NFS ¥¨¥¯¥¹¥Ý¡¼¥È¤Î°ú¤·Ñ¤®¤ò¹Ô¤¦¤È¤¤Ë¡¢
302 ¥¯¥é¥¤¥¢¥ó¥È¤ËÄÌÃΤò¹Ô¤Ã¤Æ¥Õ¥¡¥¤¥ë¥í¥Ã¥¯¤òºÆ¼èÆÀ¤¹¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤ë¡£
306 .BR /var/lib/nfs/state
308 .BR /var/lib/nfs/sm/*
310 .BR /var/lib/nfs/sm.bak/*
318 Jeff Uphoff <juphoff@nrao.edu>
320 Olaf Kirch <okir@monad.swb.de>
322 H.J. Lu <hjl@gnu.org>
324 Lon Hohberger <hohberger@missioncriticallinux.com>
326 Paul Clements <paul.clements@steeleye.com>