|
Hi Gary Camblin - good question. To change the provider were you going to change the module? It looked like the customer was against having to change the module.. if not, changing the module might work.
The description about the provider failing when changed to "provider => redhat" I'm thinking is actually surfacing a separate problem, wherein the init script itself isn't actually compatible with chkconfig and so fails..
Ie., if the init script doesn't have the chkconfig header, it won't work with chkconfig --add which is what the provider(s) use for enabling. Ie, the lines starting with something like # chkconfig: 2345 80 30
|