From: Neil Brown Date: Tue, 30 Oct 2007 01:18:34 +0000 (+1100) Subject: Make man pages configurable and exclude TCP_WRAPPERS notes where appropriate. X-Git-Url: http://git.neil.brown.name/?a=commitdiff_plain;h=be806a06d414603e0930c61d1576d47f46ff064c;p=nfs-utils.git Make man pages configurable and exclude TCP_WRAPPERS notes where appropriate. This patch makes mountd.man and statd.man able to be modified based on configuration, and removes the TCP_WRAPPERS section when that feature is not configured in. --- diff --git a/aclocal/tcp-wrappers.m4 b/aclocal/tcp-wrappers.m4 index 35ac8e0..d76c65d 100644 --- a/aclocal/tcp-wrappers.m4 +++ b/aclocal/tcp-wrappers.m4 @@ -51,4 +51,5 @@ AC_DEFUN([AC_TCP_WRAPPERS],[ AC_SUBST(LIBWRAP) AC_SUBST(HAVE_LIBWRAP) AC_SUBST(HAVE_TCP_WRAPPER) + AM_CONDITIONAL(USE_TCP_WRAPPERS, [test $HAVE_TCP_WRAPPER = 1]) ]) diff --git a/utils/mountd/Makefile.am b/utils/mountd/Makefile.am index 1e76cf8..63a441b 100644 --- a/utils/mountd/Makefile.am +++ b/utils/mountd/Makefile.am @@ -19,6 +19,16 @@ mountd_CPPFLAGS = $(AM_CPPFLAGS) $(CPPFLAGS) \ MAINTAINERCLEANFILES = Makefile.in +MAN_SED = +if USE_TCP_WRAPPERS +MAN_SED += -e 's/USE_TCP_WRAP/yes/' +else +MAN_SED += -e 's/USE_TCP_WRAP/no/' +endif + +%.man : %.man.in + sed $(MAN_SED) < $< > $@ + ####################################################################### # The following allows the current practice of having # daemons renamed during the install to include RPCPREFIX diff --git a/utils/mountd/mountd.man b/utils/mountd/mountd.man deleted file mode 100644 index 4276663..0000000 --- a/utils/mountd/mountd.man +++ /dev/null @@ -1,200 +0,0 @@ -.\" -.\" mountd(8) -.\" -.\" Copyright (C) 1999 Olaf Kirch -.\" Modified by Paul Clements, 2004. -.TH rpc.mountd 8 "31 Aug 2004" -.SH NAME -rpc.mountd \- NFS mount daemon -.SH SYNOPSIS -.BI "/usr/sbin/rpc.mountd [" options "]" -.SH DESCRIPTION -The -.B rpc.mountd -program implements the NFS mount protocol. When receiving a MOUNT -request from an NFS client, it checks the request against the list of -currently exported file systems. If the client is permitted to mount -the file system, -.B rpc.mountd -obtains a file handle for requested directory and returns it to -the client. -.SS Exporting NFS File Systems -Making file systems available to NFS clients is called -.IR exporting . -.P -Usually, a file system and the hosts it should be made available to -are listed in the -.B /etc/exports -file, and invoking -.B exportfs -a -whenever the system is booted. The -.BR exportfs (8) -command makes export information available to both the kernel NFS -server module and the -.B rpc.mountd -daemon. -.P -Alternatively, you can export individual directories temporarily -using -.BR exportfs 's -.IB host : /directory -syntax. -.SS The rmtab File -For every mount request received from an NFS client, -.B rpc.mountd -adds an entry to the -.B /var/lib/nfs/rmtab -file. When receiving an unmount request, that entry is removed. -.P -However, this file is mostly ornamental. One, the client can continue -to use the file handle even after calling -.B rpc.mountd 's -UMOUNT procedure. And two, if a client reboots without notifying -.B rpc.mountd , -a stale entry will remain in -.BR rmtab . -.SH OPTIONS -.TP -.B \-d kind " or " \-\-debug kind -Turn on debugging. Valid kinds are: all, auth, call, general and parse. -.TP -.B \-F " or " \-\-foreground -Run in foreground (do not daemonize) -.TP -.B \-f " or " \-\-exports-file -This option specifies the exports file, listing the clients that this -server is prepared to serve and parameters to apply to each -such mount (see -.BR exports (5)). -By default, export information is read from -.IR /etc/exports . -.TP -.B \-h " or " \-\-help -Display usage message. -.TP -.B \-o num " or " \-\-descriptors num -Set the limit of the number of open file descriptors to num. The -default is to leave the limit unchanged. -.TP -.B \-N " or " \-\-no-nfs-version -This option can be used to request that -.B rpc.mountd -do not offer certain versions of NFS. The current version of -.B rpc.mountd -can support both NFS version 2 and the newer version 3. If the -NFS kernel module was compiled without support for NFSv3, -.B rpc.mountd -must be invoked with the option -.B "\-\-no-nfs-version 3" . -.TP -.B \-n " or " \-\-no-tcp -Don't advertise TCP for mount. -.TP -.B \-P -Ignored (compatibility with unfsd??). -.TP -.B \-p " or " \-\-port num -Force -.B rpc.mountd -to bind to the specified port num, instead of using the random port -number assigned by the portmapper. -.TP -.B \-H " or " \-\-ha-callout prog -Specify a high availability callout program, which will receive callouts -for all client mount and unmount requests. This allows -.B rpc.mountd -to be used in a High Availability NFS (HA-NFS) environment. This callout is not -needed (and should not be used) with 2.6 and later kernels (instead, -mount the nfsd filesystem on -.B /proc/fs/nfsd -). -The program will be called with 4 arguments. -The first will be -.B mount -or -.B unmount -depending on the reason for the callout. -The second will be the name of the client performing the mount. -The third will be the path that the client is mounting. -The last is the number of concurrent mounts that we believe the client -has of that path. -.TP -.BI "\-P," "" " \-\-state\-directory\-path " directory -specify a directory in which to place statd state information. -If this option is not specified the default of -.BR /var/lib/nfs -is used. -.TP -.BI "\-r," "" " \-\-reverse\-lookup" -mountd tracks IP addresses in the rmtab, and when a DUMP request is made (by -someone running showmount -a, for instance), it returns IP addresses instead -of hostnames by default. This option causes mountd to do a reverse -lookup on each IP address and return that hostname instead. Enabling this can -have a substantial negative effect on performance in some situations. -.TP -.BR "\-t N" " or " "\-\-num\-threads=N" -This option specifies the number of worker threads that rpc.mountd -spawns. The default is 1 thread, which is probably enough. More -threads are usually only needed for NFS servers which need to handle -mount storms of hundreds of NFS mounts in a few seconds, or when -your DNS server is slow or unreliable. -.TP -.B \-V " or " \-\-nfs-version -This option can be used to request that -.B rpc.mountd -offer certain versions of NFS. The current version of -.B rpc.mountd -can support both NFS version 2 and the newer version 3. -.TP -.B \-v " or " \-\-version -Print the version of -.B rpc.mountd -and exit. -.TP -.B \-g " or " \-\-manage-gids -Accept requests from the kernel to map user id numbers into lists of -group id numbers for use in access control. An NFS request will -normally (except when using Kerberos or other cryptographic -authentication) contains a user-id and a list of group-ids. Due to a -limitation in the NFS protocol, at most 16 groups ids can be listed. -If you use the -.B \-g -flag, then the list of group ids received from the client will be -replaced by a list of group ids determined by an appropriate lookup on -the server. Note that the 'primary' group id is not affected so a -.I newgroup -command on the client will still be effective. This function requires -a Linux Kernel with version at least 2.6.21. - -.SH TCP_WRAPPERS SUPPORT -This -.B rpc.mountd -version is protected by the -.B tcp_wrapper -library. You have to give the clients access to -.B rpc.mountd -if they should be allowed to use it. To allow connects from clients of -the .bar.com domain you could use the following line in /etc/hosts.allow: - -mountd: .bar.com - -You have to use the daemon name -.B mountd -for the daemon name (even if the binary has a different name). - -For further information please have a look at the -.BR tcpd (8) -and -.BR hosts_access (5) -manual pages. - -.SH SEE ALSO -.BR rpc.nfsd (8), -.BR exportfs (8), -.BR exports (5), -.BR rpc.rquotad (8). -.SH FILES -.BR /etc/exports , -.BR /var/lib/nfs/xtab . -.SH AUTHOR -Olaf Kirch, H. J. Lu, G. Allan Morris III, and a host of others. diff --git a/utils/mountd/mountd.man.in b/utils/mountd/mountd.man.in new file mode 100644 index 0000000..6ed1bef --- /dev/null +++ b/utils/mountd/mountd.man.in @@ -0,0 +1,202 @@ +.\" +.\" mountd(8) +.\" +.\" Copyright (C) 1999 Olaf Kirch +.\" Modified by Paul Clements, 2004. +.TH rpc.mountd 8 "31 Aug 2004" +.SH NAME +rpc.mountd \- NFS mount daemon +.SH SYNOPSIS +.BI "/usr/sbin/rpc.mountd [" options "]" +.SH DESCRIPTION +The +.B rpc.mountd +program implements the NFS mount protocol. When receiving a MOUNT +request from an NFS client, it checks the request against the list of +currently exported file systems. If the client is permitted to mount +the file system, +.B rpc.mountd +obtains a file handle for requested directory and returns it to +the client. +.SS Exporting NFS File Systems +Making file systems available to NFS clients is called +.IR exporting . +.P +Usually, a file system and the hosts it should be made available to +are listed in the +.B /etc/exports +file, and invoking +.B exportfs -a +whenever the system is booted. The +.BR exportfs (8) +command makes export information available to both the kernel NFS +server module and the +.B rpc.mountd +daemon. +.P +Alternatively, you can export individual directories temporarily +using +.BR exportfs 's +.IB host : /directory +syntax. +.SS The rmtab File +For every mount request received from an NFS client, +.B rpc.mountd +adds an entry to the +.B /var/lib/nfs/rmtab +file. When receiving an unmount request, that entry is removed. +.P +However, this file is mostly ornamental. One, the client can continue +to use the file handle even after calling +.B rpc.mountd 's +UMOUNT procedure. And two, if a client reboots without notifying +.B rpc.mountd , +a stale entry will remain in +.BR rmtab . +.SH OPTIONS +.TP +.B \-d kind " or " \-\-debug kind +Turn on debugging. Valid kinds are: all, auth, call, general and parse. +.TP +.B \-F " or " \-\-foreground +Run in foreground (do not daemonize) +.TP +.B \-f " or " \-\-exports-file +This option specifies the exports file, listing the clients that this +server is prepared to serve and parameters to apply to each +such mount (see +.BR exports (5)). +By default, export information is read from +.IR /etc/exports . +.TP +.B \-h " or " \-\-help +Display usage message. +.TP +.B \-o num " or " \-\-descriptors num +Set the limit of the number of open file descriptors to num. The +default is to leave the limit unchanged. +.TP +.B \-N " or " \-\-no-nfs-version +This option can be used to request that +.B rpc.mountd +do not offer certain versions of NFS. The current version of +.B rpc.mountd +can support both NFS version 2 and the newer version 3. If the +NFS kernel module was compiled without support for NFSv3, +.B rpc.mountd +must be invoked with the option +.B "\-\-no-nfs-version 3" . +.TP +.B \-n " or " \-\-no-tcp +Don't advertise TCP for mount. +.TP +.B \-P +Ignored (compatibility with unfsd??). +.TP +.B \-p " or " \-\-port num +Force +.B rpc.mountd +to bind to the specified port num, instead of using the random port +number assigned by the portmapper. +.TP +.B \-H " or " \-\-ha-callout prog +Specify a high availability callout program, which will receive callouts +for all client mount and unmount requests. This allows +.B rpc.mountd +to be used in a High Availability NFS (HA-NFS) environment. This callout is not +needed (and should not be used) with 2.6 and later kernels (instead, +mount the nfsd filesystem on +.B /proc/fs/nfsd +). +The program will be called with 4 arguments. +The first will be +.B mount +or +.B unmount +depending on the reason for the callout. +The second will be the name of the client performing the mount. +The third will be the path that the client is mounting. +The last is the number of concurrent mounts that we believe the client +has of that path. +.TP +.BI "\-P," "" " \-\-state\-directory\-path " directory +specify a directory in which to place statd state information. +If this option is not specified the default of +.BR /var/lib/nfs +is used. +.TP +.BI "\-r," "" " \-\-reverse\-lookup" +mountd tracks IP addresses in the rmtab, and when a DUMP request is made (by +someone running showmount -a, for instance), it returns IP addresses instead +of hostnames by default. This option causes mountd to do a reverse +lookup on each IP address and return that hostname instead. Enabling this can +have a substantial negative effect on performance in some situations. +.TP +.BR "\-t N" " or " "\-\-num\-threads=N" +This option specifies the number of worker threads that rpc.mountd +spawns. The default is 1 thread, which is probably enough. More +threads are usually only needed for NFS servers which need to handle +mount storms of hundreds of NFS mounts in a few seconds, or when +your DNS server is slow or unreliable. +.TP +.B \-V " or " \-\-nfs-version +This option can be used to request that +.B rpc.mountd +offer certain versions of NFS. The current version of +.B rpc.mountd +can support both NFS version 2 and the newer version 3. +.TP +.B \-v " or " \-\-version +Print the version of +.B rpc.mountd +and exit. +.TP +.B \-g " or " \-\-manage-gids +Accept requests from the kernel to map user id numbers into lists of +group id numbers for use in access control. An NFS request will +normally (except when using Kerberos or other cryptographic +authentication) contains a user-id and a list of group-ids. Due to a +limitation in the NFS protocol, at most 16 groups ids can be listed. +If you use the +.B \-g +flag, then the list of group ids received from the client will be +replaced by a list of group ids determined by an appropriate lookup on +the server. Note that the 'primary' group id is not affected so a +.I newgroup +command on the client will still be effective. This function requires +a Linux Kernel with version at least 2.6.21. + +.if 'USE_TCP_WRAP'no' .ig +.SH TCP_WRAPPERS SUPPORT +This +.B rpc.mountd +version is protected by the +.B tcp_wrapper +library. You have to give the clients access to +.B rpc.mountd +if they should be allowed to use it. To allow connects from clients of +the .bar.com domain you could use the following line in /etc/hosts.allow: + +mountd: .bar.com + +You have to use the daemon name +.B mountd +for the daemon name (even if the binary has a different name). + +For further information please have a look at the +.BR tcpd (8) +and +.BR hosts_access (5) +manual pages. +.. + +.SH SEE ALSO +.BR rpc.nfsd (8), +.BR exportfs (8), +.BR exports (5), +.BR rpc.rquotad (8). +.SH FILES +.BR /etc/exports , +.BR /var/lib/nfs/xtab . +.SH AUTHOR +Olaf Kirch, H. J. Lu, G. Allan Morris III, and a host of others. diff --git a/utils/statd/Makefile.am b/utils/statd/Makefile.am index 8a3ba4e..2efb9f9 100644 --- a/utils/statd/Makefile.am +++ b/utils/statd/Makefile.am @@ -56,6 +56,16 @@ MAINTAINERCLEANFILES = Makefile.in CLEANFILES = $(GENFILES) +MAN_SED = +if USE_TCP_WRAPPERS +MAN_SED += -e 's/USE_TCP_WRAP/yes/' +else +MAN_SED += -e 's/USE_TCP_WRAP/no/' +endif + +%.man : %.man.in + sed $(MAN_SED) < $< > $@ + ####################################################################### # The following allows the current practice of having # daemons renamed during the install to include RPCPREFIX diff --git a/utils/statd/statd.man b/utils/statd/statd.man deleted file mode 100644 index e8be9f3..0000000 --- a/utils/statd/statd.man +++ /dev/null @@ -1,197 +0,0 @@ -.\" -.\" statd(8) -.\" -.\" Copyright (C) 1999 Olaf Kirch -.\" Modified by Jeffrey A. Uphoff, 1999, 2002, 2005. -.\" Modified by Lon Hohberger, 2000. -.\" Modified by Paul Clements, 2004. -.TH rpc.statd 8 "31 Aug 2004" -.SH NAME -rpc.statd \- NSM status monitor -.SH SYNOPSIS -.B "rpc.statd [-FNL] [-d] [-?] [-n " name "] [-o " port "] [-p " port "] [-H " prog "] [-V]" -.SH DESCRIPTION -The -.B rpc.statd -server implements the NSM (Network Status Monitor) RPC protocol. -This service is somewhat misnamed, since it doesn't actually provide -active monitoring as one might suspect; instead, NSM implements a -reboot notification service. It is used by the NFS file locking service, -.BR rpc.lockd , -to implement lock recovery when the NFS server machine crashes and -reboots. -.SS Operation -For each NFS client or server machine to be monitored, -.B rpc.statd -creates a file in -.BR /var/lib/nfs/sm . -When starting, it normally runs -.B sm-notify -to iterate through these files and notify the -peer -.B rpc.statd -on those machines. -.SH OPTIONS -.TP -.B -F -By default, -.B rpc.statd -forks and puts itself in the background when started. The -.B -F -argument tells it to remain in the foreground. This option is -mainly for debugging purposes. -.TP -.B -d -By default, -.B rpc.statd -sends logging messages via -.BR syslog (3) -to system log. The -.B -d -argument forces it to log verbose output to -.B stderr -instead. This option is mainly for debugging purposes, and may only -be used in conjunction with the -.B -F -parameter. -.TP -.BI "\-n," "" " \-\-name " name -specify a name for -.B rpc.statd -to use as the local hostname. By default, -.BR rpc.statd -will call -.BR gethostname (2) -to get the local hostname. Specifying -a local hostname may be useful for machines with more than one -interfaces. -.TP -.BI "\-o," "" " \-\-outgoing\-port " port -specify a port for -.B rpc.statd -to send outgoing status requests from. By default, -.BR rpc.statd -will ask -.BR portmap (8) -to assign it a port number. As of this writing, there is not -a standard port number that -.BR portmap -always or usually assigns. Specifying -a port may be useful when implementing a firewall. -.TP -.BI "\-p," "" " \-\-port " port -specify a port for -.B rpc.statd -to listen on. By default, -.BR rpc.statd -will ask -.BR portmap (8) -to assign it a port number. As of this writing, there is not -a standard port number that -.BR portmap -always or usually assigns. Specifying -a port may be useful when implementing a firewall. -.TP -.BI "\-P," "" " \-\-state\-directory\-path " directory -specify a directory in which to place statd state information. -If this option is not specified the default of -.BR /var/lib/nfs -is used. -.TP -.B -N -Causes statd to run in the notify-only mode. When started in this mode, the -statd program will check its state directory, send notifications to any -monitored nodes, and exit once the notifications have been sent. This mode is -used to enable Highly Available NFS implementations (i.e. HA-NFS). -This mode is deprecated \- -.B sm-notify -should be used directly instead. -.TP -.BR -L , " --no-notify -Inhibits the running of -.BR sm-notify . -If -.B sm-notify -is run by some other script at boot time, there is no need for -.B statd -to start sm-notify itself. This can be appropriate if starting of -statd needs to be delayed until it is actually need. In such cases -.B sm-notify -should still be run at boot time. -.TP -.BI "\-H, " "" " \-\-ha-callout " prog -Specify a high availability callout program, which will receive callouts -for all client monitor and unmonitor requests. This allows -.B rpc.statd -to be used in a High Availability NFS (HA-NFS) environment. The -program will be run with 3 arguments: The first is either -.B add-client -or -.B del-client -depending on the reason for the callout. -The second will be the name of the client. -The third will be the name of the server as known to the client. -.TP -.B -? -Causes -.B rpc.statd -to print out command-line help and exit. -.TP -.B -V -Causes -.B rpc.statd -to print out version information and exit. - - - -.SH TCP_WRAPPERS SUPPORT -This -.B rpc.statd -version is protected by the -.B tcp_wrapper -library. You have to give the clients access to -.B rpc.statd -if they should be allowed to use it. To allow connects from clients of -the .bar.com domain you could use the following line in /etc/hosts.allow: - -statd: .bar.com - -You have to use the daemon name -.B statd -for the daemon name (even if the binary has a different name). - -For further information please have a look at the -.BR tcpd (8) -and -.BR hosts_access (5) -manual pages. - -.SH SIGNALS -.BR SIGUSR1 -causes -.B rpc.statd -to re-read the notify list from disk -and send notifications to clients. This can be used in High Availability NFS -(HA-NFS) environments to notify clients to reacquire file locks upon takeover -of an NFS export from another server. - -.SH FILES -.BR /var/lib/nfs/state -.br -.BR /var/lib/nfs/sm/* -.br -.BR /var/lib/nfs/sm.bak/* -.SH SEE ALSO -.BR rpc.nfsd(8), -.BR portmap(8) -.SH AUTHORS -.br -Jeff Uphoff -.br -Olaf Kirch -.br -H.J. Lu -.br -Lon Hohberger -.br -Paul Clements diff --git a/utils/statd/statd.man.in b/utils/statd/statd.man.in new file mode 100644 index 0000000..d30159c --- /dev/null +++ b/utils/statd/statd.man.in @@ -0,0 +1,199 @@ +.\" +.\" statd(8) +.\" +.\" Copyright (C) 1999 Olaf Kirch +.\" Modified by Jeffrey A. Uphoff, 1999, 2002, 2005. +.\" Modified by Lon Hohberger, 2000. +.\" Modified by Paul Clements, 2004. +.TH rpc.statd 8 "31 Aug 2004" +.SH NAME +rpc.statd \- NSM status monitor +.SH SYNOPSIS +.B "rpc.statd [-FNL] [-d] [-?] [-n " name "] [-o " port "] [-p " port "] [-H " prog "] [-V]" +.SH DESCRIPTION +The +.B rpc.statd +server implements the NSM (Network Status Monitor) RPC protocol. +This service is somewhat misnamed, since it doesn't actually provide +active monitoring as one might suspect; instead, NSM implements a +reboot notification service. It is used by the NFS file locking service, +.BR rpc.lockd , +to implement lock recovery when the NFS server machine crashes and +reboots. +.SS Operation +For each NFS client or server machine to be monitored, +.B rpc.statd +creates a file in +.BR /var/lib/nfs/sm . +When starting, it normally runs +.B sm-notify +to iterate through these files and notify the +peer +.B rpc.statd +on those machines. +.SH OPTIONS +.TP +.B -F +By default, +.B rpc.statd +forks and puts itself in the background when started. The +.B -F +argument tells it to remain in the foreground. This option is +mainly for debugging purposes. +.TP +.B -d +By default, +.B rpc.statd +sends logging messages via +.BR syslog (3) +to system log. The +.B -d +argument forces it to log verbose output to +.B stderr +instead. This option is mainly for debugging purposes, and may only +be used in conjunction with the +.B -F +parameter. +.TP +.BI "\-n," "" " \-\-name " name +specify a name for +.B rpc.statd +to use as the local hostname. By default, +.BR rpc.statd +will call +.BR gethostname (2) +to get the local hostname. Specifying +a local hostname may be useful for machines with more than one +interfaces. +.TP +.BI "\-o," "" " \-\-outgoing\-port " port +specify a port for +.B rpc.statd +to send outgoing status requests from. By default, +.BR rpc.statd +will ask +.BR portmap (8) +to assign it a port number. As of this writing, there is not +a standard port number that +.BR portmap +always or usually assigns. Specifying +a port may be useful when implementing a firewall. +.TP +.BI "\-p," "" " \-\-port " port +specify a port for +.B rpc.statd +to listen on. By default, +.BR rpc.statd +will ask +.BR portmap (8) +to assign it a port number. As of this writing, there is not +a standard port number that +.BR portmap +always or usually assigns. Specifying +a port may be useful when implementing a firewall. +.TP +.BI "\-P," "" " \-\-state\-directory\-path " directory +specify a directory in which to place statd state information. +If this option is not specified the default of +.BR /var/lib/nfs +is used. +.TP +.B -N +Causes statd to run in the notify-only mode. When started in this mode, the +statd program will check its state directory, send notifications to any +monitored nodes, and exit once the notifications have been sent. This mode is +used to enable Highly Available NFS implementations (i.e. HA-NFS). +This mode is deprecated \- +.B sm-notify +should be used directly instead. +.TP +.BR -L , " --no-notify +Inhibits the running of +.BR sm-notify . +If +.B sm-notify +is run by some other script at boot time, there is no need for +.B statd +to start sm-notify itself. This can be appropriate if starting of +statd needs to be delayed until it is actually need. In such cases +.B sm-notify +should still be run at boot time. +.TP +.BI "\-H, " "" " \-\-ha-callout " prog +Specify a high availability callout program, which will receive callouts +for all client monitor and unmonitor requests. This allows +.B rpc.statd +to be used in a High Availability NFS (HA-NFS) environment. The +program will be run with 3 arguments: The first is either +.B add-client +or +.B del-client +depending on the reason for the callout. +The second will be the name of the client. +The third will be the name of the server as known to the client. +.TP +.B -? +Causes +.B rpc.statd +to print out command-line help and exit. +.TP +.B -V +Causes +.B rpc.statd +to print out version information and exit. + + + +.if 'USE_TCP_WRAP'no' .ig +.SH TCP_WRAPPERS SUPPORT +This +.B rpc.statd +version is protected by the +.B tcp_wrapper +library. You have to give the clients access to +.B rpc.statd +if they should be allowed to use it. To allow connects from clients of +the .bar.com domain you could use the following line in /etc/hosts.allow: + +statd: .bar.com + +You have to use the daemon name +.B statd +for the daemon name (even if the binary has a different name). + +For further information please have a look at the +.BR tcpd (8) +and +.BR hosts_access (5) +manual pages. +.. + +.SH SIGNALS +.BR SIGUSR1 +causes +.B rpc.statd +to re-read the notify list from disk +and send notifications to clients. This can be used in High Availability NFS +(HA-NFS) environments to notify clients to reacquire file locks upon takeover +of an NFS export from another server. + +.SH FILES +.BR /var/lib/nfs/state +.br +.BR /var/lib/nfs/sm/* +.br +.BR /var/lib/nfs/sm.bak/* +.SH SEE ALSO +.BR rpc.nfsd(8), +.BR portmap(8) +.SH AUTHORS +.br +Jeff Uphoff +.br +Olaf Kirch +.br +H.J. Lu +.br +Lon Hohberger +.br +Paul Clements