First of all - an entry in /etc/inittab will start but not stop your application - so forget about it.
The proper way is to create a script in /etc/rc.d/init.d - you can call it for example mqm.
The content of the script is basically what you have posted in your own thread. Make it executable and writable for the mq group. Than create links to this script in /etc/rc.d/rc2.d ...
and you are done.
Hi,
I just learnt the shell scripting and got working on that right now. I have one problem.
Here i am having a java application that needs to be start and stop using two shell scripts, i.e., starting the java application using one shell script and stopping the application using another... (1 Reply)
#Define the Start/Stop/Status Scripts to include
SSS_SCRIPTS=( prog1 prog2 prog3 etc...... )
#Start the scripts
StartScripts()
{
for SSS in ${SSS_SCRIPTS}
do
./$SSS start
done
}
#Stop the Scripts
StopScripts()
{
for SSS in ${SSS_SCRIPTS}
do
./$SSS stop #<---I... (1 Reply)
Hello.
I have just installed solaris on my PC (standalone). It allows to reboot. But IF I shut down and the restart by pressing the button - It does not show my solaris OS and I am then forced to perform fresh installation.
Could you please let me know the fix for it - So that shutdown and... (3 Replies)
Hi,
I have to write a program to compute the checksums of files
./script.sh
I wrote the program using bash and it took me forever since I am a beginner but it works very well.
I'm getting so close to the deadline and I realised today that actually I have to use normal Bourne shell... (3 Replies)
Stop the application before shutdown the server ..
I have application need to be started with the system and also need to be stop before shutdown the system
This is the path of the application:
/usr/appstart
/usr/appstop
to start the application with the startup of the... (2 Replies)
Hi,
We have a requirement wherein we do not want to share the Oracle DB sys and system passwords to be shared with the support desk.
But they will be responsible for starting/shuting down the Database.
Is it possible to write a shell script which will read the sys and system passwords from a... (0 Replies)
Hello,
I have script that start and shutdown the application.
where should i place my script so that it can execute at my OS shutdown ?
Pls help me... (2 Replies)
Hi there,
I am wondering if I could add start/stop ksh scripts provided by 3rd party to cluster... I read that script must be ocf/lsb compliant, however, in AIX I can just set up two separate scripts for starting and stopping application. Can similar be done under RH Linux cluster?
Cheers,
c (1 Reply)
Discussion started by: cyjan
1 Replies
LEARN ABOUT OSF1
rc2
rc2(8) System Manager's Manual rc2(8)NAME
rc2 - Run command script executed when entering a multiuser run level
SYNOPSIS
rc2
DESCRIPTION
The rc2 script contains run commands that enable initialization of the system to a multiuser state; run level 2. In addition to commands
listed within the script itself, rc2 contains instructions to run certain commands found in the /sbin/rc2.d directory. The script defines
the conditions under which the commands execute; some commands run if the system is booting, other commands execute if the system is chang-
ing run levels.
By convention, files in the /sbin/rc2.d directory begin with either the letter "K" or the letter "S" and are followed by a two-digit number
and a filename; for example: K00lpd S00savecore S25uucp
In general, the system starts commands that begin with the letter "S" and stops commands that begin with the letter "K." Commands that
begin with the letter "K" run only when the system is changing run levels from a higher to a lower level. Commands that begin with the
letter "S" run in all cases. The numbering of commands in the /sbin/rc2.d directory is important since the numbers are sorted and the com-
mands are run in ascending order. Files in the /sbin/rc2.d directory are normally links to files in the /etc/init.d directory.
An entry in the inittab file causes the system to execute the rc2 run commands, for example: s2:23:wait:/sbin/rc2 < /dev/console >
/dev/console 2>&1
The following operations are typical of those that result from executing the rc2 script and the commands located in the /sbin/rc2.d direc-
tory. The operation depends on which state the system is entering or exiting. Setting the time zone Checking the current run level Stop-
ping network services and daemons Starting (or stopping) system services and daemons Starting the cron daemon Setting up paging and dump
facilities Setting up uucp files
Setting the TIMEZONE variable is one of the first operations completed by the rc2 script. This action provides the default time zone for
subsequent commands.
FILES
Specifies the command path Specifies the directory of commands that correspond to the run level
RELATED INFORMATION
Commands: init(8), rc0(8), rc3(8) delim off
rc2(8)