next up previous contents index
Next: OSPF monitor Up: Operation Guide Previous: The Gated command





gdc [ -q ] [ -n ] [ -c coresize ] [ -f filesize ] [ -m datasize ] [ -s stacksize ] [ -t seconds ] command

Gdc provides a user-oriented interface for the operation of the gated (8) routing daemon. It provides support for starting and stopping the daemon, for the delivery of signals to manipulate the daemon when it is operating, for the maintenance and syntax checking of configuration files, and for the production and removal of state dumps and core dumps.

Gdc can reliably determine gated's running state and produces a reliable exit status when errors occur, making it advantageous for use in shell scripts which manipulate gated. Commands executed using gdc and, optionally, error messages produced by the execution of those commands, are logged via the same syslogd(8) facility which gated itself uses, providing an audit trail of operations performed on the daemon.

If installed as a setuid root program gdc will allow non-root users who are members of a trusted group (by default the gdmaint group) to manipulate the routing daemon while denying access to others. The name of the user is logged along via syslogd(8) along with an indication of each command executed, for audit purposes.

The command-line options are:

These additional command-line options may be present, depending on the options used to compile gdc:

The following commands cause signals to be delivered to gated for various purpose:

By default gated obtains its configuration from a file normally named /etc/gated.conf. The gdc program also maintains several other versions of the configuration file, in particular named:

  The new configuration file. When gdc is requested to install a new configuration file, this file is renamed /etc/gated.conf.

  The old configuration file. When gdc is requested to install a new configuration file, the previous /etc/gated.conf is renamed to this name.

  The really old configuration file. Gdc retains the previous old configuration file under this name.

The following commands perform operations related to configuration files:

Check /etc/gated.conf for syntax errors. This is usefully done after changes to the configuration file but before sending a reconfig signal to the currently running gated, to ensure that there are no errors in the configuration which would cause the running gated to terminate on reconfiguration. When this command is used, gdc issues an informational message indicating whether there were parse errors or not, and if so saves the error output in a file for inspection.

Like checkconf except that the new configuration file, /etc/gated.conf+, is checked instead.

Move the /etc/gated.conf+ file into place as /etc/gated.conf, retaining the older versions of the file as described above. Gdc will decline to do anything when given this command if the new configuration file doesn't exist or otherwise looks suspect.

Rotate the configuration files in the newer direction, in effect moving the old configuration file to /etc/gated.conf. The command will decline to perform the operation if /etc/gated.conf- doesn't exist or is zero length, or if the operation would delete an existing, non-zero length /etc/gated.conf+ file.

Perform a backout operation even if /etc/gated.conf+ exists and is of non-zero length.

Set all configuration files to mode 664, owner root, group gdmaint. This allows a trusted non-root user to modify the configuration files.

If /etc/gated.conf+ does not exist, create a zero length file with the file mode set to 664, owner root, group gdmaint. This allows a trusted non-root user to install a new configuration file.

The following commands provide support for starting and stopping gated, and for determining its running state:

Determine if gated is currently running. This is done by checking to see if gated has a lock on the file containing its pid, if the pid in the file is sensible and if there is a running process with that pid. Exits with zero status if gated is running, non-zero otherwise.

Start gated. The command returns an error if gated is already running. Otherwise it executes the gated binary and waits for up to the delay interval (10 seconds by default, as set with the -t option otherwise) until the newly started process obtains a lock on the pid file. 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.

Stop gated, gracefully if possible, ungracefully if not. The command returns an error (with non-zero exit status) if gated is not currently running. Otherwise it sends a terminate signal to gated and waits for up to the delay interval (10 seconds by default, as specified with the -t option otherwise) for the process to exit. Should gated fail to exit within the delay interval it is then signaled again with a second terminate signal. Should it fail to exit by the end of the second delay interval it is signaled for a third time with a kill signal. This should force immediate termination unless something is very broken. The command terminates with zero exit status when it detects that gated has terminated, non-zero otherwise.

If gated is running it is terminated via the same procedure as is used for the stop command above. When the previous gated terminates, or if it was not running prior to command execution, a new gated process is executed using the procedures described for the start command above. A non-zero exit status is returned if any step in this procedure appears to have failed.

The following commands allow the removal of files created by the execution of some of the commands above:

Removes any existing gated core dump file.

Removes any existing gated state dump file.

Removes the parse error file generated when a checkconf or checknew command is executed and syntax errors are encountered in the configuration file being checked.

Related files

Many of default filenames listed below contain the string %s, which is replaced by the name with which gated is invoked. Normally this is gated, but if invoked as gated-test, gated will by default look for /etc/gated-test.conf. These paths may all be changed at compilation time.

the gated binary. Another popular location is /usr/local/sbin/gated.

current gated configuration file.

newer configuration file.

older configuration file

much older configuration file

where gated stores its pid, the default is /etc/ Another popular location is /var/run/

gated's state dump file, the default is /usr/tmp/%s_dump. Another popular location is /var/tmp/%s_dump.

where config file parse errors go, the default is /usr/tmp/%s_parse. Another popular location is /var/tmp/%s_parse.

where gated drops its core file. Another popular location is /var/tmp. The core file is usually core, but some systems use core.gated.


Many commands only work when gated is installed in the system directory it was configured with.

There is not yet any way to tell gdc about systems which name their core dump other than core ( core.gated is a less common possibility).

next up previous contents index
Next: OSPF monitor Up: Operation Guide Previous: The Gated command

Laurent Joncheray
Wed Jun 12 15:35:22 EDT 1996