Product SiteDocumentation Site

Chapter 28. The sysconfig Directory

28.1. Files in the /etc/sysconfig/ Directory
28.1.1. /etc/sysconfig/amd
28.1.2. /etc/sysconfig/apmd
28.1.3. /etc/sysconfig/arpwatch
28.1.4. /etc/sysconfig/authconfig
28.1.5. /etc/sysconfig/autofs
28.1.6. /etc/sysconfig/clock
28.1.7. /etc/sysconfig/desktop
28.1.8. /etc/sysconfig/dhcpd
28.1.9. /etc/sysconfig/exim
28.1.10. /etc/sysconfig/firstboot
28.1.11. /etc/sysconfig/gpm
28.1.12. /etc/sysconfig/hwconf
28.1.13. /etc/sysconfig/i18n
28.1.14. /etc/sysconfig/init
28.1.15. /etc/sysconfig/ip6tables-config
28.1.16. /etc/sysconfig/iptables-config
28.1.17. /etc/sysconfig/irda
28.1.18. /etc/sysconfig/keyboard
28.1.19. /etc/sysconfig/kudzu
28.1.20. /etc/sysconfig/named
28.1.21. /etc/sysconfig/network
28.1.22. /etc/sysconfig/nfs
28.1.23. /etc/sysconfig/ntpd
28.1.24. /etc/sysconfig/radvd
28.1.25. /etc/sysconfig/samba
28.1.26. /etc/sysconfig/selinux
28.1.27. /etc/sysconfig/sendmail
28.1.28. /etc/sysconfig/spamassassin
28.1.29. /etc/sysconfig/squid
28.1.30. /etc/sysconfig/system-config-securitylevel
28.1.31. /etc/sysconfig/system-config-selinux
28.1.32. /etc/sysconfig/system-config-users
28.1.33. /etc/sysconfig/system-logviewer
28.1.34. /etc/sysconfig/tux
28.1.35. /etc/sysconfig/vncservers
28.1.36. /etc/sysconfig/xinetd
28.2. Directories in the /etc/sysconfig/ Directory
28.3. Additional Resources
28.3.1. Installed Documentation
The /etc/sysconfig/ directory contains a variety of system configuration files for Red Hat Enterprise Linux.
This chapter outlines some of the files found in the /etc/sysconfig/ directory, their function, and their contents. The information in this chapter is not intended to be complete, as many of these files have a variety of options that are only used in very specific or rare circumstances.

28.1. Files in the /etc/sysconfig/ Directory

The following sections offer descriptions of files normally found in the /etc/sysconfig/ directory. Files not listed here, as well as extra file options, are found in the /usr/share/doc/initscripts-<version-number>/sysconfig.txt file (replace <version-number> with the version of the initscripts package). Alternatively, looking through the initscripts in the /etc/rc.d/ directory can prove helpful.

Note

If some of the files listed here are not present in the /etc/sysconfig/ directory, then the corresponding program may not be installed.
The /etc/sysconfig/init file controls how the system appears and functions during the boot process.
The following values may be used:
  • BOOTUP=<value>, where <value> is one of the following:
    • color — The standard color boot display, where the success or failure of devices and services starting up is shown in different colors.
    • verbose — An old style display which provides more information than purely a message of success or failure.
    • Anything else means a new display, but without ANSI-formatting.
  • RES_COL=<value>, where <value> is the number of the column of the screen to start status labels. The default is set to 60.
  • MOVE_TO_COL=<value>, where <value> moves the cursor to the value in the RES_COL line via the echo -en command.
  • SETCOLOR_SUCCESS=<value>, where <value> sets the success color via the echo -en command. The default color is set to green.
  • SETCOLOR_FAILURE=<value>, where <value> sets the failure color via the echo -en command. The default color is set to red.
  • SETCOLOR_WARNING=<value>, where <value> sets the warning color via the echo -en command. The default color is set to yellow.
  • SETCOLOR_NORMAL=<value>, where <value> resets the color to "normal" via the echo -en.
  • LOGLEVEL=<value>, where <value> sets the initial console logging level for the kernel. The default is 3; 8 means everything (including debugging), while 1 means only kernel panics. The syslogd daemon overrides this setting once started.
  • PROMPT=<value>, where <value> is one of the following boolean values:
    • yes — Enables the key check for interactive mode.
    • no — Disables the key check for interactive mode.

28.1.17. /etc/sysconfig/irda

The /etc/sysconfig/irda file controls how infrared devices on the system are configured at startup.
The following values may be used:
  • IRDA=<value>, where <value> is one of the following boolean values:
    • yesirattach runs and periodically checks to see if anything is trying to connect to the infrared port, such as another notebook computer trying to make a network connection. For infrared devices to work on the system, this line must be set to yes.
    • noirattach does not run, preventing infrared device communication.
  • DEVICE=<value>, where <value> is the device (usually a serial port) that handles infrared connections. A sample serial device entry could be /dev/ttyS2.
  • DONGLE=<value>, where <value> specifies the type of dongle being used for infrared communication. This setting exists for people who use serial dongles rather than real infrared ports. A dongle is a device that is attached to a traditional serial port to communicate via infrared. This line is commented out by default because notebooks with real infrared ports are far more common than computers with add-on dongles. A sample dongle entry could be actisys+.
  • DISCOVERY=<value>, where <value> is one of the following boolean values:
    • yes — Starts irattach in discovery mode, meaning it actively checks for other infrared devices. This must be turned on for the machine to actively look for an infrared connection (meaning the peer that does not initiate the connection).
    • no — Does not start irattach in discovery mode.

28.1.22. /etc/sysconfig/nfs

NFS requires portmap, which dynamically assigns ports for RPC services. This causes problems for configuring firewall rules. To overcome this problem, use the /etc/sysconfig/nfs file to control which ports the required RPC services run on.
The /etc/sysconfig/nfs may not exist by default on all systems. If it does not exist, create it and add the following variables (alternatively, if the file exists, un-comment and change the default entries as required):
MOUNTD_PORT=x
control which TCP and UDP port mountd (rpc.mountd) uses. Replace x with an unused port number.
STATD_PORT=x
control which TCP and UDP port status (rpc.statd) uses. Replace x with an unused port number.
LOCKD_TCPPORT=x
control which TCP port nlockmgr (rpc.lockd) uses. Replace x with an unused port number.
LOCKD_UDPPORT=x
control which UDP port nlockmgr (rpc.lockd) uses. Replace x with an unused port number.
If NFS fails to start, check /var/log/messages. Normally, NFS will fail to start if you specify a port number that is already in use. After editing /etc/sysconfig/nfs restart the NFS service by running the service nfs restart command. Run the rpcinfo -p command to confirm the changes.
To configure a firewall to allow NFS:
  1. Allow TCP and UDP port 2049 for NFS.
  2. Allow TCP and UDP port 111 (portmap/sunrpc).
  3. Allow the TCP and UDP port specified with MOUNTD_PORT="x"
  4. Allow the TCP and UDP port specified with STATD_PORT="x"
  5. Allow the TCP port specified with LOCKD_TCPPORT="x"
  6. Allow the UDP port specified with LOCKD_UDPPORT="x"