NAME<\/a> chkconfig \u2212 updates and queries runlevel information for system services<\/p>\n chkconfig<\/b> [–list<\/b>] [–type<\/b> type<\/i>] [name<\/i>] chkconfig<\/b><\/i> provides a simple command-line tool for maintaining the \/etc\/rc0.d \/etc\/rc1.d \/etc\/rc2.d \/etc\/rc3.d \/etc\/rc4.d \/etc\/rc5.d \/etc\/rc6.d directory hierarchy by relieving system administrators of the task of directly manipulating the numerous symbolic links in those directories.<\/p>\n This implementation of chkconfig<\/b> was inspired by the chkconfig<\/b> command present in the IRIX operating system. Rather than maintaining configuration information outside of the \/etc\/rc0.d \/etc\/rc1.d \/etc\/rc2.d \/etc\/rc3.d \/etc\/rc4.d \/etc\/rc5.d \/etc\/rc6.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<\/i> starts in a single location.<\/p>\n chkconfig<\/b> has five distinct functions: adding new services for management, removing services from management, listing the current startup information for services, changing the startup information for services, and checking the startup state of a particular service.<\/p>\n When chkconfig<\/b> 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<\/b> returns true; otherwise it returns false. The –level<\/b> option may be used to have chkconfig<\/b> query an alternative runlevel rather than the current one.<\/p>\n When chkconfig<\/b> is run with the –list<\/b> argument, or no arguments at all, a listing is displayed of all services and their current configuration.<\/p>\n If one of on<\/b>, off<\/b>, reset<\/b>, or resetpriorities<\/b> is specified after the service name, chkconfig<\/b> changes the startup information for the specified service. The on<\/b> and off<\/b> flags cause the service to be started or stopped, respectively, in the runlevels being changed. The reset<\/b> 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<\/b> flag resets the start\/stop priorities for the service to whatever is specified in the init script.<\/p>\n By default, the on<\/b> and off<\/b> options affect only runlevels 2, 3, 4, and 5, while reset<\/b> and resetpriorities<\/b> affects all of the runlevels. The –level<\/b> option may be used to specify which runlevels are affected.<\/p>\n 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 running.<\/p>\n chkconfig<\/b> also can manage xinetd scripts via the means of xinetd.d configuration files. Note that only the on<\/b>, off<\/b>, and -\u2212list<\/b> commands are supported for xinetd.d services.<\/p>\n chkconfig<\/b> supports a -\u2212type<\/b> argument to limit actions to only a specific type of services, in the case where services of either type may share a name. Possible values for type<\/i> are sysv<\/i> and xinetd<\/i>.<\/p>\n -\u2212level<\/b> levels<\/i><\/p>\n 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<\/b> specifies runlevels 3 and 5.<\/p>\n -\u2212no-redirect<\/b><\/p>\n 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 redirection to systemd and only operates on the symlinks in \/etc\/rc[0-6].d. This option is only valid when on<\/b>, off<\/b>, or no command (to check enablement) is passed to a service.<\/p>\n -\u2212add<\/b> name<\/i><\/p>\n This option adds a new service for management by chkconfig<\/b>. When a new service is added, chkconfig<\/b> ensures that the service has either a start or a kill entry in every runlevel. If any runlevel is missing such an entry, chkconfig<\/b> creates the appropriate entry as specified by the default values in the init script. Note that default entries in LSB-delimited \u2019INIT INFO\u2019 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.<\/p>\n -\u2212del<\/b> name<\/i><\/p>\n The service is removed from chkconfig<\/b> management, and any symbolic links in \/etc\/rc0.d \/etc\/rc1.d \/etc\/rc2.d \/etc\/rc3.d \/etc\/rc4.d \/etc\/rc5.d \/etc\/rc6.d which pertain to it are removed.<\/p>\n Note that future package installs for this service may run chkconfig \u2212\u2212add<\/b>, which will re-add such links. To disable a service, run chkconfig<\/b> name<\/i> off<\/b>.<\/p>\n -\u2212override<\/b> name<\/i><\/p>\n If service name<\/i> is configured exactly as it would be if the -\u2212add<\/b> option had been specified with no override file in \/etc\/chkconfig.d\/name<\/i>, and if \/etc\/chkconfig.d\/name<\/i> now exists and is specified differently from the base initscript, change the configuration for service name<\/i> to follow the overrides instead of the base configuration.<\/p>\n -\u2212list<\/b> name<\/i><\/p>\n This option lists all of the services which chkconfig<\/b> knows about, and whether they are stopped or started in each runlevel. If name<\/i> is specified, information in only display about service name<\/i>.<\/p>\n Each service which should be manageable by chkconfig<\/b> needs two or more commented lines added to its init.d script. The first line tells chkconfig<\/b> 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 \u2212<\/b> 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 continuation.<\/p>\n For example, random.init has these three lines:<\/p>\n 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.<\/p>\n chkconfig also supports LSB-style init stanzas, and will apply them in preference to “chkconfig:” lines where available. A LSB stanza looks like:<\/p>\n 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.<\/p>\n Files in \/etc\/chkconfig.d\/servicename<\/i> are parsed using the same comments that chkconfig notices in init service scripts, and override values in the init service scripts themselves.<\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
RUNLEVEL FILES<\/a>
OVERRIDE FILES<\/a>
SEE ALSO<\/a>
AUTHOR<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
chkconfig –add<\/b> name<\/i>
chkconfig –del<\/b> name<\/i>
chkconfig –override<\/b> name<\/i>
chkconfig<\/b> [–level<\/b> levels<\/i>] [–type<\/b> type<\/i>] [–no-redirect<\/b>] name<\/i> <on<\/b>|off<\/b>|reset<\/b>|resetpriorities<\/b>>
chkconfig<\/b> [–level<\/b> levels<\/i>] [–type<\/b> type<\/i>] [–no-redirect<\/b>] name<\/i><\/p>\nDESCRIPTION <\/a> <\/h2>\n
OPTIONS <\/a> <\/h2>\n
RUNLEVEL FILES <\/a> <\/h2>\n
# chkconfig: 2345 20 80 # description: Saves and restores system entropy pool for # higher quality random number generation.<\/pre>\n
### 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<\/pre>\n
OVERRIDE FILES <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n