Enabling and Disabling Network Daemons

This section explains how to enable and disable the following network daemons:

• rwhod

• routed

• gated

• writesrv

You can choose to run either the routed or the gated daemon; however, you cannot run both.

11.2.1 Running the rwhod Daemon

The rwho daemon (rwhod) maintains the database used by the rwho and ruptime commands. Running rwhod is optional; however, it must be running to use these commands.

11.2.1.1 Starting and Enabling the rwho Daemon To start the rwhod daemon, perform the following steps:

1. If the network is started, check to see if the rwhod daemon is running by issuing the following command:

# /bin/ps ax

I

grep rwhod

2. If the network is started and the rwhod daemon is not running, enter the following command to start the rwhod daemon in the background:

# /usr/sbin/rwhod

If you enable the rwhod daemon, it is started automatically by the /sbin/init.d/rwho script each time the network is restarted or the system is rebooted. Use the rcmgr command to modify the entry for the

Manually Setting Up the Network 11-5

rwhod daemon in the / etc / rc • conf i g file:

# /usr/sbin/rcmgr set RWHOD yes

11.2.1.2 Stopping and Disabling the rwho Daemon To stop the rwhod daemon, perform the following steps:

1. Check to see if the rwhod daemon is running by issuing the following command:

# /bin/ps ax

I

grep rwhod

2. If the rwhod daemon is running, kill the process by issuing a /bin/kill command with the process ID (PID) for the daemon obtained from the /bin/ps command.

If you disable the rwhod daemon, it is not started automatically by the / sbin/ ini t . d/ rwho script each time you restart the network or reboot the system. Use the following rcmgr command to disable the rwhod daemon in the /etc/rc .config file:

# /usr/sbin/rcmgr set RWHOD no

For more information, see rwhod(8).

11.2.2 Running the routed Daemon

The routed daemon automatically updates the internal routing tables in your host. It does this by using the Routing Information Protocol (RIP).

Running the routed daemon is optional.

Note

You cannot run both the routed daemon and the gated daemon on your system.

11.2.2.1 Starting and Enabling the routed Daemon

To start the routed daemon on your system, perform the following steps:

1. If the network is started, check to see whether the routed daemon is running by issuing the following command:

# /bin/ps ax

I

grep routed

2. If you want to add static routes, use the procedure in Section 11.4.

3. If the network is started and the routed daemon is not running, you can start the routed daemon with or without flags.

To start the routed daemon without flags, enter the following 11-6 Manually Setting Up the Network

command:

# /usr/sbin/routed

To start the routed daemon with flags, include the flags in the command line, separating each flag with a space. For example, the following command starts the routed daemon with the -s flag, which causes the routed daemon to supply RIP information even if it is not functioning as an Internet router:

# /usr/sbin/routed -s

For more information, see routed(8).

If you enable the routed daemon, it is started automatically by the I sbinl ini t. dl route script each time the network is restarted or the system is rebooted. To enable the routed daemon, perform the following steps:

1. Use the following rcmgr command to enable the routed daemon:

# /usr/sbin/rcmgr set ROUTED yes

2. Check to see if the routed daemon flags are set in letc/rc .config, using the following rcmgr command:

# /usr/sbin/rcmgr get ROUTED_FLAGS

If flags are set and you do not want any routed daemon flags, reset the flags in letc/rc .config, using the following rcmgr command:

# /usr/sbin/rcmgr set ROUTED_FLAGS "

If you want to change the routed daemon flags, reset the flags in I etc I rc . conf ig, using the rcmgr command. Enclose the flags in double quotation marks and separate each flag with a space.

See routed(8) for more information.

11.2.2.2 Stopping and Disabling the routed Daemon To stop the routed daemon, perform the following steps:

1. Check to see if the routed daemon is running by issuing the following command:

# /bin/ps ax

I

grep routed

2. If the routed daemon is running, kill the process by issuing a Ibin/kill command with the process ID (PID) for the daemon obtained from the Ibin/ps command.

If you disable the routed daemon, it is not started automatically by the Isbin/init.d/route script each time you restart the network or reboot the system. To disable the routed daemon, perform the following steps:

Manually Setting Up the Network 11-7

1. Use the following rcmgr command to disable the routed daemon:

# /usr/sbin/rcmgr set ROUTED no

2. If the routed daemon flags are set, you can reset the flags in the / etc / rc . conf i g file by issuing the following rcmgr command:

# /usr/sbin/rcmgr set ROUTED_FLAGS ..

See routed(8) for more information.

11.2.3 Running the gated Daemon

The gated daemon automatically updates the internal routing tables in your host. It can do this using multiple routing protocols. Running the gated daemon is optional.

Note

You cannot run both the routed daemon and the gated daemon on your system.

11.2.3.1 Starting and Enabling the gated Daemon To start the gated daemon, perform the following steps:

1. If the network is started, check to see whether the gated daemon is running by issuing the following command:

# /bin/ps ax

I

grep gated

2. The / etc/ gated. conf file contains configuration information that is read by the gated daemon. If the / etc/ gated. conf file does not exist, set it up in the format specified in gated. conf(4).

If the / etc / gated. conf file exists, you can modify it if needed.

If the gated daemon is running when you modify the

/etc/gated.conf file, the gated daemon detects the changes and they take effect immediately. Otherwise, the changes take effect when you manually start the gated daemon.

3. If you want to add static routes, use the procedure in Section 11.4.

4. If the network is started and the gated daemon is not running, you can start it with or without flags.

11-8 Manually Setting Up the Network

To start the gated daemon without flags, issue the following command:

# lusrlsbin/gated

To start the gated daemon with flags, include the flags in the command line, separating each flag with a space. For example, the following command starts the gated daemon with the -r flag, which causes the gated daemon to log all routing changes:

# lusrlsbin/gated -r

For more information, see gated(8).

If you enable the gated daemon, it is started automatically by the

/ sbin/ ini t . d/ gateway script each time the network is restarted or the system is rebooted. To enable the gated daemon, perform the following steps:

1. Use the following rcrngr command to enable the gated daemon:

# lusrlsbin/rcmgr set GATED yes

2. Check to see if the gated daemon flags are set in the

/ etc / rc . conf ig file, using the following rcrngr command:

# lusrlsbin/rcmgr get GATED_FLAGS

If flags are set and you do not want any gated daemon flags, reset the flags in the / etc / rc . conf ig file, using the following rcrngr command:

# lusrlsbin/rcmgr set GATED_FLAGS "

If you want to change the gated daemon flags, reset the flags in the / etc / rc . conf ig file, using the rcrngr command. Enclose the flags in double quotation marks and separate each flag with a space.

See gated(8) for more information.

11.2.3.2 Stopping and Disabling the gated Daemon To stop the gated daemon, perform the following steps:

1. Check to see if the gated daemon is running by issuing the following command:

# Ibin/ps ax

I

grep gated

2. If the gated daemon is running, kill the process by issuing a /bin/kill command with the process ID (PID) for the daemon obtained from the /bin/ps command.

If you disable the gated daemon, it is not started automatically by the / sbin/ ini t. d/ gateway script each time you restart the network or reboot the system. To disable the gated daemon, perform the following

Manually Setting Up the Network 11-9

steps:

1. Use the following rcmgr command to disable the gated daemon:

# lusrlsbin/rcmgr set GATED no

2. If gated daemon flags are set, you can reset the flags in the / etc / rc . conf i g file, using the following rcmgr command:

# lusrlsbin/rcmgr set GATED_FLAGS "

See gated(8) for more information.

11.2.4 Running the writesrv Daemon

The writesrv daemon receives remote write command requests.

Running wri tesrv is optional; however, it must be running to use the following options with the wr i te command:

• -h

• -q

• - r

11.2.4.1 Starting and Enabling the writesrv Daemon

To start the writesrv daemon, perform the following steps:

1. If the network is started, check to see if the wr i te s rv daemon is running by issuing the following command:

# Ibin/ps ax

I

grep writesrv

2. If the network is started and the wri tesrv daemon is not running, enter the following command to start the wri tesrv daemon in the

background:

# lusrlsbin/writesrv

If you enable the wr i tesrv daemon, it is started automatically by the / sbin/ ini t. d/wri te script each time the network is restarted or the system is rebooted. Use the rcmgr command to modify the entry for the writesrv daemon in the /etc/rc .config file:

# lusrlsbin/rcmgr set WRITESRV yes

11.2.4.2 Stopping and Disabling the writesrv Daemon To stop the wri tesrv daemon, perform the following steps:

11-10 Manually Setting Up the Network

1. Check to see if the wr i tesrv daemon is running by issuing the following command:

# /bin/ps ax

I

grep writesrv

2. If the wri tesrv daemon is running, kill the process by issuing a /bin/kill command with the process 10 (PID) for the daemon obtained from the /bin/ps command.

If you disable the wr i tesrv daemon, it is not started automatically by the /sbin/init.d/write script each time you restart the network or reboot the system. Use the following rcmgr command to disable the wri tesrv daemon in the /etc/rc. config file:

# /usr/sbin/rcmgr set WRITESRV no

For more information, see wri tesrv(8).

Dans le document DEC OSF/l (Page 134-140)