At this moment you've already solved this problem, I guess. But I had a similar problem which almost made me bold and I finally managed to fix it.
And I have a feeling that some people would appreciate some of this knowledge.
To make your service runnable at boot you have to run the following commands:
// add your script to chkconfig which updates and queries runlevel information for system services
chkconfig --add <my_script>
// see if your service was added to chkconfig
// In this example I'm selecting runlevels 2, 3 and 4 for my script. To see more information about runlevels, google chkconfig (I'm not allowed to post links for some reason because my account is new... )
// don't forget to enable the script by saying "on" at the end of the command
chkconfig --level 234 <my_script> on
Another solution is to set chkconfig settings directly into your script:
# chkconfig: 234 10 60
# description: My awesome script
This part of the init script is what chkconfig looks for, and, in this instance, it tells chkconfig that the service should start at run levels 2, 3 and 4,
it should be turned off for all other run levels (chkconfig's default assumption) and that it should have a start priority of 10 and a stop priority of 60.
The priority numbers that you include in your script are relative and shouldn't generally be an issue. The defaults are usually 20 and 80.
You can also add a "#description:" line (directly after the required chkconfig line) to your script if you want to be able to see that in chkconfig output, but it's not necessary.