If you check what is in /etc/rc0.d and /etc/rc6.d, you will see that before you get to your service, the system will have run first a killall (priority 00), and then a halt (priority 01).
Although your service were scheduled to run next, the computer did already halt.
lrwxrwxrwx 1 root root 17 Sep 28 2012 S00killall -> ../init.d/killall
lrwxrwxrwx 1 root root 14 Sep 28 2012 S01halt -> ../init.d/halt
lrwxrwxrwx 1 root root 14 Jul 8 21:16 S10test -> ../init.d/test
What I'd do if I were you, is to enable the script in runlevels you typically use, say 345 and then swap start with stop, as all daemons which is chkconfig:ed to be running in your current runlevel will be called when halting and rebooting with the stop arg, before it gets to the services which it should start.
If you want your script to be run at the very last, before killing everything and then halting your computer, check what is the highest (mine's K92iptables, so for me that would be >92 for stop priority).
So chkconfig --del baseRhel64 first, then alter the script so that chkconfig line reads # chkconfig: 345 10 93
Your script would then look something like this, with start and stop function names swapped:
#!/bin/sh
#chkconfig --list
# chkconfig: 345 10 93
stop(){
echo "`basename $0` stop"
touch /root/installscripts/test1
}
start(){
echo "`basename $0` start"
touch /root/installscripts/test2
touch /root/installscripts/"`basename $0`"
}
case "$1" in
start) start;;
stop) stop;;
*);;
echo $"Usage: $0 {start|stop}"
RETCAL=1
esac
exit 0