Specifies the name of the configuration file. If this option is not specified, scspd looks for the file /etc/scspd.conf.
Specifies that scspd is to be run in debug mode. In debug mode, the daemon is not put into the background. Log messages are written to standard output instead of to the log file specified in the configuration file.
Specifies that scspd will trace specified events and messages as it executes. The -T flag is followed by one or more of the following options:
trace s CA Finite State Machine (FSM),
trace s Hello FSM,
trace s Client Interface FSM,
trace CA, CSUS, CSU Request, and CSU Reply messages,
The only protocol supported by the current version of scspd is ATMARP. The protocol statement must always be specified.
The netif statement specifies the name of the ATM network interface on which a client server is providing service. The netif statement must always be specified.
The ServerGroupID statement specifies an identifier for the group of servers being synchronized by scspd. The ID is specified as a decimal number in the range 0 - 65,535. The server group ID must be the same for all servers whose caches are being synchronized by an SCSP session. That is, the server group ID for a host must be the same for all Directly Connected Servers (DCSs) pointed to within a server statement. The ServerGroupID statement must always be specified.
The familyID statement specifies an identifier for a family of parallel SCSP sessions running between a group of hosts (i.e., a set of SCSP sessions with different protocol IDs but the same set of servers). The ID is specified as a decimal number in the range 0 - 65,535. The family ID is currently not used by scspd.
The ATMaddr statement specifies the ATM address of the DCS. The ATMaddr statement must always be specified.
The ID statement specifies the SCSP identifier of the DCS. For ATMARP, the ID is the IP address or DNS name associated with the ATM interface of the DCS. The ID statement must always be specified.
The CAReXmitInt statement specifies the interval that is allowed to elapse between retransmissions of CA messages. If a CA message is sent and an acknowledgement is not received within CAReXmitInt seconds, the message will be retransmitted. The default value for CAReXmitInt is 3 seconds.
The CSUSReXmitInt statement specifies the interval that is allowed to elapse between retransmissions of CSU Solicit messages. When a CSUS message is sent, any Cache State Advertisements (CSAs) requested by the CSUS that have not been received within CSUSReXmitInt seconds will be requested again by another CSUS message. The default value for CSUSReXmitInt is 3 seconds. Be careful not to confuse CSUSReXmitInt and CSUReXmitInt.
The CSUReXmitInt statement specifies the interval that is allowed to elapse between retransmissions of CSU Request messages. When a CSU Request message is sent, any CSAs that are not acknowledged by a CSU Reply message within CSUReXmitInt seconds will be retransmitted. The default value for CSUReXmitInt is 2 seconds. Be careful not to confuse CSUReXmitInt and CSUSReXmitInt.
The CSUReXmitMax statement specifies the number of times that a CSA will be retransmitted as described above before SCSP gives up on the CSA and discards it. The default value for CSUReXmitMax is 5.
The HelloDead statement specifies the Hello Dead Factor that will be sent to the DCS in Hello messages. A ""DCS down"" condition will be detected when nothing is received from a DCS in HelloDead * HelloInt seconds. The default value for HelloDead is 3.
The HelloInt statement specifies the Hello Interval that will be sent to the DCS in Hello messages. The default value for HelloInt is 3 seconds.
The Hops statement specifies the number of hops (DCS to DCS) that will be specified in CSAs originating from the local server. This number must be at least as large as the diameter of the server group. That is, it must be large enough for a CSA to be propagated from server to server all the way across the server group. The default value for Hops is 3.
scspd default configuration file name. A different file name can be specified with the -f command-line option.
.Sm off /tmp/scspd. <pid> . <seq> .out .Sm on
debugging information dump file name. The scspd utility writes a summary of its control blocks to this file when it receives a SIGINT signal. <pid> is the process ID of the daemon and <seq> is a sequence number which is incremented every time a dump is taken.
.Sm off /tmp/scspd. <pid> .trace .Sm on
trace file. The scspd utility writes trace information to this file if the -T option is specified on the command line.