Red Hat

Server: Redhat 6.2
Goal: Startup script/Shutdown Script
Overview: I'm just doing a very basic test. I'm not getting chkconfig involved.
Research so far: I've found a few different ways of getting this to work, some say I can just drop the scripts in the corresponding rc directory. Others recommend dropping the scripts /etc/init and using chkconfig to create the symlinks and manage them as services. Eventually I want to get to the chkconfig level but right now I just want two scripts, one for startup and one for shutdown. I haven't been able to get any of the methods I've found to work so I decided to start as small as possible and build up from there.


Steps so far:
Two files:

Code:

#cat /etc/rc3.d/S98test
echo "Starting rc3 test" > /tmp/rc3starttest

and

Code:

#cat /etc/rc3.d/K01test
touch /var/lock/subsys/K01test
echo "Stopping rc3 test" > /tmp/rc3stoptest

inittab is set for runlevel 3.

I'm probably violating so many standards this way. I just wanted a very very low level test for startup/shutdown scripts. S98test runs fine, on reboot the file is in /tmp. K01test seems to be doing nothing. After reboot there is no file in /tmp.

Is there a question in there somewhere?

The stop script is not working

lock files are removed during a restart / shutdown. Given that a lock file must exist before a Kill script is run, creating it in the Kill script is pointless when entering any runlevel from a restart. Your file would be created, however, if you switched to runlevel 3 from either single user mode (init 1) or X (init 5).

Code:

(start VM)
[root@test1 tmp]# ll /tmp/rc3*
-rw-r--r--. 1 root root 18 May 16 13:49 /tmp/rc3starttest
[root@test1 tmp]# init 1
[root@test1 tmp]# init 3
[root@test1 tmp]# ll /tmp/rc3*
-rw-r--r--. 1 root root 18 May 16 13:49 /tmp/rc3starttest
-rw-r--r--. 1 root root 18 May 16 13:51 /tmp/rc3stoptest

The Kill script should go at the runlevel you expect to enter when switching to a new runlevel (i.e. shutdown (0), reboot (6) or back to 3 from single user mode (1) or X (5)) as said. It usually doesn't make sense to have the start and stop scripts at the same runlevel, since why would you want to stop something before you started it?

Ahhh very nice.

I put myself in a Catch-22 of sorts. That helps clarify many many things. Thanks Scott