Account Links: Cart | Register | Log In

Skip to content

Red Hat Enterprise Linux (version 3) Documentation Errata

If you find any errors in the Red Hat Enterprise Linux documentation, or just have a suggestion, please read the Submitting Documentation Errata page.

Reference Guide

OpenLDAP Setup Overview

The command listed for starting the slapd service is incorrect. The correct command is as follows:

/sbin/service ldap start

bonding Module Directives

The list of available parameters for the bonding module has been expanded. The complete list is as follows:

  • 0 — Sets a round-robin policy for fault tolerance and load balancing. Transmissions are received and sent out sequentially on each bonded slave interface beginning with the first one available.

  • 1 — Sets an active-backup policy for fault tolerance. Transmissions are received and sent out via the first available bonded slave interface. Another bonded slave interface is only used if the active bonded slave interface fails.

  • 2 — Sets an XOR (exclusive-or) policy for fault tolerance and load balancing. Using this method the interface matches up the incoming request's MAC address with the MAC address for one of the slave NICs. Once this link is established, transmissions are sent out sequentially beginning with the first available interface.

  • 3 — Sets a broadcast policy for fault tolerance. All transmissions are sent on all slave interfaces.

  • 4 — Sets a IEEE 802.3ad dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives on all slaves in the active aggregator. Requires a switch that is 802.3ad compliant.

  • 5 — Sets a Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. The outgoing traffic is distributed according to the current load on each slave interface. Incoming traffic is received by the current slave. If the receiving slave fails another slave takes over the MAC address of the failed slave.

  • 6 — Sets a Active Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for IPV4 traffic. The receive load balancing is achieved by ARP negotiation.


/etc/sysconfig/desktop

The passage describing the /etc/sysyconfig/desktop file is incorrect. The passage should read:

The /etc/sysconfig/desktop file specifies the desktop for new users and the display manager to be run when entering runlevel 5.

Correct values are:

DESKTOP=<value>, where <value> is one of the following:

  • GNOME — Selects the GNOME desktop environment.

  • KDE — Selects the KDE desktop environment.

DISPLAYMANAGER=<value>, where <value> is one of the following:

  • GNOME — Selects the GNOME Display Manager.

  • KDE — Selects the KDE Display Manager.

  • XDM — Selects the X Display Manager.

Securing Email Client Communications

You must remove the existing imapd.pem and ipop3d.pem files before running the make imapd.pem and make ipop3d.pem commands. The passage should read as follows:

To create a self-signed SSL certificate for IMAP, change to the /usr/share/ssl/certs/ directory and type the following commands as root:

rm -f imapd.pem
make imapd.pem

Answer all of the questions to complete the process.

To create a self-signed SSL certificate for POP, change to the /usr/share/ssl/certs/ directory, and type the following commands as root:

rm -f ipop3d.pem
make ipop3d.pem

Again, answer all of the questions to complete the process.

Important
 

Be sure to remove the default imapd.pem and ipop3d.pem files before issuing each make command.

Once finished, execute the /sbin/service xinetd restart command to restart the xinetd daemon which controls imapd and ipop3d.

Runlevel 3

The path to the Xclients file is incorrect. The sentence should read:

If .Xclients does not exist in the user's home directory, the standard /etc/X11/xinit/Xclients script attempts to start another desktop environment, trying GNOME first and then KDE followed by twm.

Top-level Files within the proc File System

Running cat /proc/stat lists 7 fields in the cpu output, not 4 as shown in the example. A correct example of running cat /proc/stat is the following: 

cpu  209841 1554 21720 118519346 72939 154 27168
cpu0 42536 798 4841 14790880 14778 124 3117
cpu1 24184 569 3875 14794524 30209 29 3130
cpu2 28616 11 2182 14818198 4020 1 3493
cpu3 35350 6 2942 14811519 3045 0 3659
cpu4 18209 135 2263 14820076 12465 0 3373
cpu5 20795 35 1866 14825701 4508 0 3615
cpu6 21607 0 2201 14827053 2325 0 3334
cpu7 18544 0 1550 14831395 1589 0 3447
page 477934 1073889
swap 1 0
intr 15239682 14857833 6 0 6 6 0 5 0 1 0 0 0 29 0 2 0 0 0 0 0 0 0
94982 0 286812
disk_io:
ctxt 4209609
btime 1078711415
processes 21905
procs_running 1
procs_blocked 0

The cpu output measures the number of jiffies (1/100th of a second) that the system has been in user mode, user mode with low priority (nice), system mode, idle task, I/O wait, hardirq (IRQ), and softirq. The IRQ output is a direct response while the softirq output runs at a lower priority than the IRQ and therefore may be interrupted more frequently. The total for all CPUs on a system is shown in the cpu output, while each individual CPU is listed below it with its own statistics. The example is a 4-way Intel Pentium Xeon configuration with multithreading enabled, which is displayed as four physical processors and four virtual processors.

Zone Files

The values for the $ORIGIN directive in the example zone files are incorrect. The correct values for the respective files are:

$ORIGIN example.com.

and

$ORIGIN 1.0.10.in-addr.arpa.

The trailing dot after each value makes the value absolute rather than relative domain names for unqualified records.



Red Hat Cluster Suite Configuring and Managing a Cluster

Decreasing the Kernel Boot Timeout Limit

The GRUB boot timeout limit is specified in seconds and not tenths of a second. The sentence should read:

When using the GRUB boot loader, the timeout parameter in /boot/grub/grub.conf should be modified to specify the appropriate number of seconds for the timeout parameter.

Installation Notes for Red Hat Enterprise Linux 2.1 Users

The command listed in step 7 for converting the cluster configuration file is incorrect. The sentence should read:

Invoke the /usr/sbin/cluster-convert command to convert the /etc/cluster.conf to /etc/cluster.xml.