I've been working on changes to chkconfig to allow you to specify overrides to chkconfig information in initscripts. Suppose that you have an initscript called /etc/init.d/foo that starts something like this:

#!/bin/bash
# chkconfig: - 23 87
...

That initscript will not be started by default; you would have to manually run chkconfig foo on for that script to start automatically.

With my changes, you will be able to create /etc/chkconfig.d/foo with lines that override any special chkconfig-parsed comments, like this:

# chkconfig: 345 15 85

Then with that file in place, the chkconfig --add foo command will cause your foo service to be automatically started in runlevels 3, 4, and 5.

I have written the part that allows chkconfig to parse the new files for --add. Next, I'm going to work on code to apply overrides after the fact. Right now I'm using the --override option, but if anyone has better suggestions for the name, I'm all ears...