CHKCONFIG(8)CHKCONFIG(8)NAMEchkconfig - updates and queries runlevel information for system ser‐
SYNOPSISchkconfig [--list] [--type type] [name]
chkconfig [--level levels] [--type type] [--no-redirect] name
chkconfig [--level levels] [--type type] [--no-redirect] name
DESCRIPTIONchkconfig provides a simple command-line tool for maintaining the
/etc/rc[0-6].d directory hierarchy by relieving system administrators
of the task of directly manipulating the numerous symbolic links in
This implementation of chkconfig was inspired by the chkconfig command
present in the IRIX operating system. Rather than maintaining configu‐
ration information outside of the /etc/rc[0-6].d hierarchy, however,
this version directly manages the symlinks in /etc/rc[0-6].d. This
leaves all of the configuration information regarding what services
init starts in a single location.
chkconfig has five distinct functions: adding new services for manage‐
ment, removing services from management, listing the current startup
information for services, changing the startup information for ser‐
vices, and checking the startup state of a particular service.
When chkconfig is run with only a service name, it checks to see if the
service is configured to be started in the current runlevel. If it is,
chkconfig returns true; otherwise it returns false. The --level option
may be used to have chkconfig query an alternative runlevel rather than
the current one.
When chkconfig is run with the --list argument, or no arguments at all,
a listing is displayed of all services and their current configuration.
If one of on, off, reset, or resetpriorities is specified after the
service name, chkconfig changes the startup information for the speci‐
fied service. The on and off flags cause the service to be started or
stopped, respectively, in the runlevels being changed. The reset flag
resets the on/off state for all runlevels for the service to whatever
is specified in the init script in question, while the resetpriorities
flag resets the start/stop priorities for the service to whatever is
specified in the init script.
By default, the on and off options affect only runlevels 2, 3, 4, and
5, while reset and resetpriorities affects all of the runlevels. The
--level option may be used to specify which runlevels are affected.
Note that for every service, each runlevel has either a start script or
a stop script. When switching runlevels, init will not re-start an
already-started service, and will not re-stop a service that is not
chkconfig also can manage xinetd scripts via the means of xinetd.d con‐
figuration files. Note that only the on, off, and --list commands are
supported for xinetd.d services.
chkconfig supports a --type argument to limit actions to only a spe‐
cific type of services, in the case where services of either type may
share a name. Possible values for type are sysv and xinetd.
Specifies the run levels an operation should pertain to. It is
given as a string of numbers from 0 to 6. For example, --level
35 specifies runlevels 3 and 5.
When chkconfig is run on a system that uses systemd as its init
system, chkconfig will forward commands to systemd if a systemd
service file exists for it. This switch turns off the redirect‐
ion to systemd and only operates on the symlinks in
/etc/rc[0-6].d. This option is only valid when on, off, or no
command (to check enablement) is passed to a service.
This option adds a new service for management by chkconfig.
When a new service is added, chkconfig ensures that the service
has either a start or a kill entry in every runlevel. If any
runlevel is missing such an entry, chkconfig creates the appro‐
priate entry as specified by the default values in the init
script. Note that default entries in LSB-delimited 'INIT INFO'
sections take precedence over the default runlevels in the
initscript; if any Required-Start or Required-Stop entries are
present, the start and stop priorities of the script will be
adjusted to account for these dependencies.
The service is removed from chkconfig management, and any sym‐
bolic links in /etc/rc[0-6].d which pertain to it are removed.
Note that future package installs for this service may run chk‐
config --add, which will re-add such links. To disable a ser‐
vice, run chkconfig name off.
If service name is configured exactly as it would be if the
--add option had been specified with no override file in
/etc/chkconfig.d/name, and if /etc/chkconfig.d/name now exists
and is specified differently from the base initscript, change
the configuration for service name to follow the overrides
instead of the base configuration.
This option lists all of the services which chkconfig knows
about, and whether they are stopped or started in each runlevel.
If name is specified, information in only display about service
Each service which should be manageable by chkconfig needs two or more
commented lines added to its init.d script. The first line tells chk‐
config what runlevels the service should be started in by default, as
well as the start and stop priority levels. If the service should not,
by default, be started in any runlevels, a - should be used in place of
the runlevels list. The second line contains a description for the
service, and may be extended across multiple lines with backslash con‐
For example, random.init has these three lines:
# chkconfig: 2345 20 80
# description: Saves and restores system entropy pool for \
# higher quality random number generation.
This says that the random script should be started in levels 2, 3, 4,
and 5, that its start priority should be 20, and that its stop priority
should be 80. You should be able to figure out what the description
says; the \ causes the line to be continued. The extra space in front
of the line is ignored.
chkconfig also supports LSB-style init stanzas, and will apply them in
preference to "chkconfig:" lines where available. A LSB stanza looks
### BEGIN INIT INFO
# Provides: foo
# Required-Start: bar
# Defalt-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Description: Foo init script
### END INIT INFO
In this case, the start priority of "foo" would be changed such that it
is higher than the "bar" start priority, if "bar" is enabled. Care
must be taken when adding dependencies, as they can cause vast shifts
in the start and stop priorities of many scripts.
File in /etc/chkconfig.d/servicename are parsed using the same comments
that chkconfig notices in init service scripts, and override values in
the init service scripts themselves.
Erik Troan <email@example.com>
4th Berkeley Distribution Wed Oct 8 1997 CHKCONFIG(8)