rdc(1M)rdc(1M)NAMErdc - user interface for Routing Administration Manager (RAMD)
SYNOPSIS
coresize] filesize] seconds]
DESCRIPTION
provides a user-oriented interface for working with the and routing
daemons. and are referred to as routing daemons. provides a command-
line interface to start and stop these daemons. In addition, it pro‐
vides commands to check the configuration file for syntax errors, make
the daemon dump core, and dump the current state of the daemon.
can reliably determine the running state of the routing protocols.
This can be used in shell scripts to manipulate
Options
supports the following command-line options:
Specifies that does not change the kernel forwarding table while run‐
ning and routing daemons. This option is useful to test the daemons,
when the daemons should operate as a route server that does not for‐
ward.
Suppresses the stderr messages of
and routing daemons. This option can be used to suppress infor‐
mational messages that are normally printed to the standard out‐
put, and the log error messages through syslogd(1M).
Specifies the time in seconds for which
waits to start, stop, reconfigure and terminate daemons. By
default, this value is set to 10 seconds.
Specifies the maximum size of a core dump
produced by the routing daemons invoked using
Specifies the maximum size of a file produced
or created by the routing daemons invoked using
Commands
The following commands are used to send HP-UX signals to or routing
daemons for various purposes:
Sends an abort signal to the requested daemon and terminates the daemon
with a core dump. The core files are generated in the file where can
be or
Sends a signal to the requested daemon to dump its current
state into the where is one of the routing daemons.
Kills the daemon abruptly.
This command is used when the daemon hangs.
Sends signal to the requested daemon to reread its configuration file
and reconfigure its current state.
Sends signal to the requested daemon to terminate gracefully.
Sends signal to the daemon to toggle the trace. If tracing is
enabled, this command causes tracing to be suspended and the
trace file to be closed. If tracing is disabled, the trace file
is reopened and tracing initiated. This is useful to move the
trace files. If or the routing daemon tracing is modified using
this command and the daemons are reconfigured with the trace
options, the effect on tracing is with respect to the configura‐
tion file.
Sends signal to to recheck the interface configuration. periodically
checks the kernel interface configuration for any changes. This
command can be used to force the daemon to check the interface
status immediately. Currently, the only valid argument for this
command is for checking on
By default, obtains its configuration information from the file. main‐
tains many versions of the configuration file. The versions of the
configuration file maintained by are as follows:
command of
is used to create this configuration file.
When must install a new configuration file using the command,
the existing file is renamed as file.
When creates a new configuration file, using the command, the
existing file is renamed as and the existing is renamed
as file.
Configuration File Commands
The following commands perform operations related to configuration
files:
Checks for syntax errors. This is done after changes are made to the
configuration file and before reconfiguring the routing daemons. The
system administrator use this command to ensure that there are no syn‐
tax errors in the configuration file, which can otherwise terminate the
daemons on reconfiguration.
Checks the
file for syntax errors.
Renames the
file to retaining the older versions of the configuration files.
This operation fails if does not exist.
Replaces the old configuration file
to This command fails, if the file does not exist or if the file
is of zero length, or if the backout command deletes an exist‐
ing, non-zero length file.
Performs a
operation even if the file exists and is of non-zero length.
Sets all configuration files to mode 664, owner root and
group trusted non-root user. This allows a trusted non-root
user to modify the configuration files.
Creates a new configuration file,
with zero length. The file mode is set to 664, owner root and
group trusted non-root user. This allows a trusted non-root
user to install a new configuration file.
Controlling Daemons
The following commands can be used to control the daemons:
Starts The command returns an error if is already running. It invokes
and waits for the time period specified with option. A non-zero exit
status is returned, if an error is detected while executing the binary,
or if a lock is not obtained on the pid file within the specified wait
time. Starting invokes all the configured protocols in the configura‐
tion file of
The following commands can be used to determine the current state of
the daemon or to stop or restart and other IPv6 routing protocols.
Determines if daemons are currently running. exits with a zero status
if the daemon is running and with a non-zero value if the daemons are
not running.
Stops the requested routing daemon gracefully.
Stopping stops all the daemons.
Restarts the requested daemon.
reports an error, if there is a failure.
EXAMPLES
To start type the following at the HP-UX command prompt:
If successful, the pid of the daemon is displayed.
To get the current state of the daemons, type the following at command
prompt:
This will dump the current state of the and routing daemons.
The dump files for the and routing daemons are and respectively; where
is one of the routing daemons.
To reconfigure the routing daemons, change the configuration file and
issue the following command at the command prompt:
AUTHOR
was developed by Future software Ltd.
FILES
where, can be or the routing daemons.
SEE ALSOkill(1), ram_monitor(1M), ramd(1M), syslogd(1M), signal(2),
ramd.conf(4).
rdc(1M)
