© 2004 A.P. Lawrence
The script lacks a 'chkconfig' comment line
To be managed by chkconfig, a script has to have comment lines that chkconfig can read. Here's a sample from xinetd:
# chkconfig: 345 56 50 # description: xinetd is a powerful replacement for inetd. \ # xinetd has access control mechanisms, extensive \ # logging capabilities, the ability to make services \ # available based on time, and can place \ # limits on the number of servers that can be started, \ # among other things.
That says that xinetd starts at levels 3,4 and 5, that its start script will be named S56xinted, and that its stop script will be K50xinetd.
These comments are NOT changed if you use chkconfig to change when a service runs; they are merely the initial condition.
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
/Tests/Linux/e0860.html copyright Tony Lawrence All Rights Reserved
| Views for this page | ||||
|---|---|---|---|---|
| Today | This Week | This Month | This Year | Overall |
| 1 | 1 | 1 | 364 | 2,021 |
Thu Aug 14 20:05:40 2008 chkconfig error MichaelFoy
Website:
the description tag is also required for some versions of chkconfig to
work.
Add your comments