[root]# chkconfig –list gated gated 0:off 1:off 2:off 3:off 4:off 5:off 6:off [root]# chkconfig –level 35 gated on [root]# chkconfig –list gated gated 0:off 1:off 2:off 3:on 4:off 5:on 6:off Of course, you don’t have to wait for the system to reboot to run gated. On a Red Hat 7.1 system gated is started by the script /etc/init.d/gated, which can be run from the shell prompt, as follows: [root]# service gated start Not starting gated: [ OK ] Not starting! This is not what we expected. When the script runs successfully, the message displayed is “starting gated”. However, the script file will not attempt to start gated unless a gated configuration is provided. gated is configured through the /etc/gated.conf file. If we had scrolled through the list of files that Figure 7.4 shows for the gated RPM, we would have found that Red Hat does not provide a preconfigured gated.conf file. If you want to run gated, you must build your own configuration. The gated.conf File At startup, gated reads the gated.conf file. The file contains configuration statements that tell gated which routing protocols should be run and how they should be configured. There are several types of configuration statements: Options statements Interface statements Definition statements Protocol statements Static statements Control statements Aggregate statements Not all of these statements are required for a configuration, but when they are used, the statements must appear in the order listed here. These statements can be divided into two groups: statements you probably won’t use and statements you might use. Among the statements you’re unlikely to use are the options statements, the static statements, the control statements, and the aggregate statements: The options statements set parameters such as nosend (don’t send any routing information) and noresolv (don’t use DNS), which are used only for special configurations. The static statements define the static routes that should be included in the routing table. Generally, when you run a routing protocol, you don’t need to define static routes. The control statements are used to define the routing policy. They are primarily used when passing routing between routing domains. Although it is unlikely that you will be using Linux for this, an example of using control statements appears later because it is one of the key features of gated. The aggregate statements are used to aggregate routes within regional and national networks to reduce the number of routes exchanged between national networks. The statements that you are more likely to use in a Linux gated configuration are defin-ition statements, interface statements, and protocol statements: 220
Note: If you are looking for cheapest and affordable webspace to host and run your servlet application check Astra servlet hosting services