Sponsored Content
Full Discussion: statd
Special Forums IP Networking statd Post 3346 by ngagne on Friday 29th of June 2001 10:14:52 AM
Old 06-29-2001
statd

I am trying to set up a SunOS 4.1.3 system on our local ethernet. This system had been previously installed on another network. When I boot the system, I get an error saying "rpc.statd cannot talk to statd on[name]". I configured the IP address according to our network scheme (192.9.200.x) and rewrote the host table.

What is this error and how do I resolve it? Also, how do you set subnet masks? This system was given to us by one of our customers, and no documentation was included.

Thanks in advance,
Nate Gagne
 

3 More Discussions You Might Find Interesting

1. Cybersecurity

NFS security issues with lockd and statd

We are trying to implement a NAS solution with UNIX servers and multiple networks, and I've heard that NFS has security issues with lockd and statd. The security issue as it was explained to me is that these services are subject to vulnerabilities/exploits, and that users who connect to Unix... (1 Reply)
Discussion started by: onceagain
1 Replies

2. SCO

Upgrade current version of statd

Dear All, I have sco Unix release 5 and i was asked to Upgrade the current version of statd. kindly guide Regards (1 Reply)
Discussion started by: sak900354
1 Replies

3. AIX

statd -a can't get ip configuration

Hi, I am new in AIX. Here is a problem I have now: I've got an error in console saying: "statd -a can't get ip configuration: A file or directory in the path name does not exist." How can I troubleshoot the issue? Where should a get start from? Thank you in advance! ---------- Post... (1 Reply)
Discussion started by: aixlover
1 Replies
rpc.statd(8)						      System Manager's Manual						      rpc.statd(8)

NAME
rpc.statd - NSM status monitor 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 actu- ally provide active monitoring as one might suspect; instead, NSM implements a reboot notification 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/statd/sm. When starting, 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 gethostname(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 status 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 writ- ing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing a firewall. -? 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 following 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/statd/sm/state /var/lib/nfs/statd/sm/* /var/lib/nfs/statd/sm.bak/* SEE ALSO
rpc.nfsd(8), portmap(8) AUTHORS
Jeff Uphoff <juphoff@transmeta.com> Olaf Kirch <okir@monad.swb.de> H.J. Lu <hjl@gnu.org> Lon Hohberger <hohberger@missioncriticallinux.com> 08 Mar 2001 rpc.statd(8)
All times are GMT -4. The time now is 07:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy