Doesn't the file also need to be in one of the rc#.d?
I would think so -- but since the wiki wants it in /etc/init.d, I'd start by putting it there, rebooting to see what happens, then fixing any subsequent problems.
When I want to automatically start custom apps on SME, I add them to /etc/e-smith/events/local as described
here so that they run after all other startup services, connections, etc.
I suspect that the technically correct placement for /etc/init.d/vbox on a "normal" CentOS box booting to runlevel 7 (as the SME seems to do based on
who -r) would be:
1) create /etc/rc.d/init.d/vbox with the content shown in the wiki
2) make it executable with
chmod +x /etc/rc.d/init.d/vbox2) create a symlink in /etc/rc.d/rc7.d using
cd /etc/rc.d/rc7.d
ln -s ../init.d/vbox S99vbox(Note that SME has some more options that integrate this process with the config db -- allowing you to enable and disable services using a command like 'config setprop vbox enabled'. Read more at
http://wiki.contribs.org/SME_Server:Documentation:Developers_Manual#Run-level_7_and_the_e-smith-service_wrapper)
[guess]
If you effect the auto-startup by creating /etc/rc.d/rc7.d/S99vbox, you probably need to add a "Kxxvbox" in either /etc/rc.d/rc0.d or /etc/rc.d/rc6.d to get vbox to shutdown politely. Choose "xx" so that your script sorts alphabetically before any services that vbox is dependant on - 'K00vbox'
If you create a script for auto-start in /etc/e-smith/events/local, you would also want to add scripts to /etc/e-smith/events/halt and /etc/e-smith/events/reboot to generate polite shutdowns.
[/guess]