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
statd(1M)																 statd(1M)

NAME
statd, rpc.statd - network status monitor SYNOPSIS
DESCRIPTION
is an RPC server. It interacts with to provide the crash and recovery functions for the locking services on NFS (see lockd(1M)). keeps track of the clients with processes which hold locks on a server. When the server reboots after a crash, sends a message to the on each client indicating that the server has rebooted. The client processes then informs the on the client that the server has rebooted. The client then attempts to reclaim the lock(s) from the server. on the client host also informs the on the server(s) holding locks for the client when the client has rebooted. In this case, the on the server informs its that all locks held by the rebooting client should be released, allowing other processes to lock those files. Options recognizes the following options and command-line arguments: This is an obsolete option. All messages and errors are logged to WARNINGS
The crash of a server is only detected upon its recovery. FILES
lists hosts and network addresses to be contacted after a reboot lists hosts and network addresses that could not be contacted after last reboot includes a number which changes during a reboot AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
lockd(1M), fcntl(2), lockf(2), signal(2), sm(4). statd(1M)
All times are GMT -4. The time now is 05:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy