4.2. Service Initialization
Xinetd is a daemon used to start network services on demand. The changes in xinetd are related to the allowed limit of open file descriptors:
The listening mechanism has changed from
poll(). With this change, the limit of open file descriptors used by xinetd can be changed.
File descriptor limit can also now be changed on a per-service basis. This can be done in the configuration file for the service via the
rlimit_files directive. The value can be a positive integer or UNLIMITED.
In Red Hat Enterprise Linux 6, the custom runlevels 7, 8 and 9 are no longer supported and can not be used.
In Red Hat Enterprise Linux 6, init from the sysvinit package has been replaced with Upstart, an event-based init system. This system handles the starting of tasks and services during boot, stopping them during shutdown and supervising them while the system is running. For more information on Upstart itself, refer to the
init(8) man page.
Processes are known to Upstart as jobs and are defined by files in the
/etc/init directory. Upstart is very well documented via man pages. Command overview is in
init(8) and job syntax is described in
Upstart provides the following behavioral changes in Red Hat Enterprise Linux 6:
/etc/inittab file is deprecated, and is now used only for setting up the default runlevel via the initdefault line. Other configuration is done via upstart jobs in the
The number of active tty consoles is now set by the ACTIVE_CONSOLES variable in
/etc/sysconfig/init, which is read by the
/etc/init/start-ttys.conf job. The default value is ACTIVE_CONSOLES=/dev/tty[1-6], which starts a getty on tty1 through tty6.
A serial getty is still automatically configured if the serial console is the primary system console. In prior releases, this was done by
kudzu, which would edit
/etc/inittab. In Red Hat Enterprise Linux 6, configuration of the primary serial console is handled by
To configure a getty running on a non-default serial console, you must now write an Upstart job instead of editing
/etc/inittab. For example, if a getty on ttyS1 is desired, the following job file (
/etc/init/serial-ttyS1.conf) would work:
# This service maintains a getty on /dev/ttyS1.
start on stopped rc RUNLEVEL=
stop on starting runlevel 
exec /sbin/agetty /dev/ttyS1 115200 vt100-nav
As in prior releases, you should still make sure that ttyS1 is in
/etc/securetty if you wish to allow root logins on this getty.
Because of the move to Upstart, using
/etc/shutdown.allow for defining who can shut the machine down is no longer supported.