Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Kitty Hooch

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 64 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

rpc.statd



SYNOPSIS

       /sbin/rpc.statd [-F] [-d] [-?] [-n  name ] [-o  port ] [-p
       port ] [-V]


DESCRIPTION

       The rpc.statd server implements the  NSM  (Network  Status
       Monitor) RPC protocol.  This service is somewhat misnomed,
       since it doesn't actually provide active monitoring as one
       might  suspect; instead, NSM implements a reboot notifica­
       tion service. It is used by the NFS file locking  service,
       rpc.lockd,  to implement lock recovery when the NFS server
       machine crashes and reboots.

   Operation
       For each NFS client or server  machine  to  be  monitored,
       rpc.statd  creates a file in /var/lib/nfs/sm.  When start­
       ing, it iterates through these files and notifies the peer
       rpc.statd on those machines.


OPTIONS

       -F     By  default, rpc.statd forks and puts itself in the
              background when started. The -F argument  tells  it
              to  remain in the foreground. This option is mainly
              for debugging purposes.

       -d     By default, rpc.statd sends  logging  messages  via
              syslog(3) to system log.  The -d argument forces it
              to log  verbose  output  to  stderr  instead.  This
              option  is  mainly  for debugging purposes, and may
              only be used in conjunction with the -F  parameter.

       -n, --name name
              specify  a  name  for rpc.statd to use as the local
              hostname. By default, rpc.statd will call  gethost­
              name(2)  to  get  the  local hostname. Specifying a
              local hostname may be useful for machines with more
              than one interfaces.

       -o, --outgoing-port port
              specify  a port for rpc.statd to send outgoing sta­
              tus requests from.  By default, rpc.statd will  ask
              portmap(8)  to assign it a port number.  As of this
              writing, there is not a standard port  number  that
              portmap  always  or  usually assigns.  Specifying a
              port may be useful when implementing a firewall.

       -p, --port port
              specify a port for  rpc.statd  to  listen  on.   By
              default, rpc.statd will ask portmap(8) to assign it
              a port number.  As of this writing, there is not  a
              standard port number that portmap always or usually
              assigns.  Specifying a  port  may  be  useful  when

       -?     Causes rpc.statd to print out command-line help and
              exit.

       -V     Causes  rpc.statd  to print out version information
              and exit.


TCP_WRAPPERS SUPPORT

       This rpc.statd version is  protected  by  the  tcp_wrapper
       library.  You have to give the clients access to rpc.statd
       if they should be allowed to use  it.  To  allow  connects
       from clients of the .bar.com domain you could use the fol­
       lowing line in /etc/hosts.allow:

       statd: .bar.com

       You have to use the daemon name statd for the daemon  name
       (even if the binary has a different name).

       For  further information please have a look at the tcpd(8)
       and hosts_access(5) manual pages.


FILES

       /var/lib/nfs/state
       /var/lib/nfs/sm/*
       /var/lib/nfs/sm.bak/*


SEE ALSO

       rpc.nfsd(8), portmap(8)


AUTHORS

       Jeff Uphoff <juphoff@nrao.edu>
       Olaf Kirch <okir@monad.swb.de>
       H.J. Lu <hjl@gnu.org>
       Lon Hohberger <hohberger@missioncriticallinux.com>

                           16 Sep 2002               rpc.statd(8)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =


  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.05 Seconds