statd Post: 3349

Sponsored Content

Special Forums IP Networking statd Post 3349 by Optimus_P on Friday 29th of June 2001 10:48:37 AM

06-29-2001

Registered User

i dont have the answer for your statd problem

but there is where you can set your subnet.

Code:

(hostname):/etc # cat /etc/netmasks
#
# The netmasks file associates Internet Protocol (IP) address
# masks with IP network numbers.
#
#       network-number  netmask
#
# The term network-number refers to a number obtained from the Internet Network
# Information Center.  Currently this number is restricted to being a class
# A, B, or C network number.  In the future we should be able to support
# arbitrary network numbers per the Classless Internet Domain Routing
# guidelines.
#
# Both the network-number and the netmasks are specified in
# "decimal dot" notation, e.g:
#
#               128.32.0.0 255.255.255.0
#
10.0.0.0        255.255.255.0

Optimus_P

View Public Profile for Optimus_P

Find all posts by Optimus_P

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...

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

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...

LEARN ABOUT OSF1

rpc.lockd

rpc.lockd(8)						      System Manager's Manual						      rpc.lockd(8)

NAME

       rpc.lockd, lockd - Network lock daemon

SYNOPSIS

       /usr/sbin/rpc.lockd [-b hostname] [-c] [-d debug] [-g graceperiod] [-h hashsize] [-s] [-t timeout]

OPTIONS

       The  default  behavior  will  create  and bind a socket for each protocol per interface on the system. When the -b switch is specified, one
       socket per protocol will be created and bind to the passed IP address.  Available only on TruCluster Server systems. This option starts the
       clusterwide lock daemon, which helps provide highly available NFS service. Do not use -c directly.  Highly available NFS service is config-
       ured by default and typically does not require intervention. If you do need to start the clusterwide lock  daemon,  use	the  CAA  command,
       caa_start cluster_lockd.

	      For more information, see the TruCluster Server Administration manual.  Internal Use Only.  Use this option only under the direction
	      of technical support personnel.  Causes the rpc.lockd daemon to use the variable graceperiod (in seconds) as the grace period  dura-
	      tion  instead  of  the default value of 15 seconds.  Internal Use Only.  Causes the rpc.lockd daemon to use the variable timeout (in
	      seconds) as the interval instead of the default value of 5 seconds to retransmit a lock request to the remote server.

DESCRIPTION

       The rpc.lockd daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking
       service makes this advisory locking support possible by using the fcntl system call and the lockf subroutine. The rpc.lockd daemon forwards
       lock requests for remote data to the server site's lock daemon. The rpc.lockd daemon then requests the status  monitor  daemon,	rpc.statd,
       for monitor service. The reply to the lock request is not sent to the kernel until the status daemon and the server site's lock daemon have
       replied.

       If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until  all
       daemons become available.

       When  a server recovers, it waits for a grace period for all client site lock daemons to submit reclaim requests.  Client site lock daemons
       are notified by rpc.statd of the server recovery and promptly resubmit previously granted lock requests.  If a client  site's  lock  daemon
       fails  to secure previously granted locks at the server site, it sends the signal SIGLOST to all the processes that were previously holding
       locks and cannot reclaim them.

SEE ALSO

       Commands: rpc.statd(8)

       Functions: fcntl(2), signal(2), lockf(3)

																      rpc.lockd(8)