help auto starting app on boot Post: 302326197

Sponsored Content

Operating Systems HP-UX help auto starting app on boot Post 302326197 by thenomad on Wednesday 17th of June 2009 10:03:40 AM

06-17-2009

Registered User

HP's startup stuff can be a little tricky if you don't know what you are doing. Having said that, it ain't no magic at all.

I am assuming you have a startup/shutdown script for your database right ? If yes, place them in /sbin/init.d directory to be compliant with the standards (otherwise they can be placed anywhere)

Then, decide on which run-level it needs to start, 1 thru 4. The rc script at the startup time, goes thru these run-levels in an ascending order. Run level directories are
$ ll -d /sbin/rc*d
dr-xr-xr-x 2 bin bin 1024 May 6 14:09 /sbin/rc0.d
dr-xr-xr-x 2 bin bin 3072 May 6 2008 /sbin/rc1.d
dr-xr-xr-x 2 bin bin 3072 May 6 14:09 /sbin/rc2.d
dr-xr-xr-x 2 bin bin 1024 Feb 13 2008 /sbin/rc3.d
dr-xr-xr-x 2 bin bin 96 Apr 25 2007 /sbin/rc4.d

rc0.d is reserved for shutting down the system related processes, like syncer, LVM daemon and what-not and unless your database is an integral part of your OS, you should not be placing anything there.

Since these run levels get executed in ascending order, you need to know what prerequisites need to be running prior to launching your database and decide where your startup needs to go. Most layered products like databases and such, usually start at run-level 3

In each run level, you will see symbolic links to start up scripts placed in (generally) /sbin/init.d, named similar to "SxxxScriptName.sh", where the xxx is a numeric sequence number. When the rc script runs, it goes through the numbers, yes, as you guessed, in an ascending order.

In each run level you also will see symbolic links starting with letter K. Those are the "Kill" scripts. Kill scripts are placed one run-level above the level application starts. Highest numbered S script usually complimented by the lowest numbered K script in the next run level above this one.

so, if we say you will start your database as the last app on run level 3, it needs to be killed as first thing on run level 4, so hypothetical commands you will need to run are as follows:

cp /path/to/my/database_start_stop_script /sbin/init.d

ln -s /sbin/rc3.d/S900MyDbStart /sbin/init.d/database_start_stop_script
ln -s /sbin/rc2.d/K100MyDbStop /sbin/init.d/database_start_stop_script

make sure your start/stop script has execute permissions and your links are not destroying existing links (if so, adjust the xxx values by few numbers above or below)

Hope this helps

thenomad

View Public Profile for thenomad

Find all posts by thenomad

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Auto Boot

Ok when i reboot my machine its a pain in the A** i do not have a monitor on it and i know its going to eventualy ask me to type BOot and then its going to ask me if i want to interact with the........ and then it will boot up fine... Hp UX 11i is what i am running and i would like it to boot...

2. Slackware

starting up something on boot

I'm trying to bring up a database server when the linux 6.2 machine is restarted, in unix i can set up a Sxxdbstart script under rc3.d and run su user -c /path/to/my/script How can I do this in linux? I thought I could just run it under the rc.d/rc.local script and add it at the end of the...

3. Shell Programming and Scripting

how to capture my app starting up.

This is the script for the cold backup that we get from mycat every time it goes down and up again. It's a huge email that we get and all within the body. Here is the dilemma; I would like to capture just the ��successful start up of the luminis app.�� I don't know if I need to do an �if...

4. Solaris

Auto fsck -y at boot

Does anyone know how or if its possible to automatically run fsck -y at boot if the initial fsck check finds that there has been data lost. Usually the initial fsck check will fix low level inconsistencies but if it finds that data has been lost it will put you into single user mode for you to log...

5. Shell Programming and Scripting

error situation handling when starting app from a script

Hi, in my bash script I start 3rd party app that runs quickly normally and returns some data that I use later for processing. However if there are problems the app doesn't return anything and just hangs... then my script also hangs of course, awaiting for the app to comeback. Was wondering how to...

6. UNIX for Beginners Questions & Answers

Howto auto boot SPARC | How to auto supply "start /SYS" and "start /SP/console" commands

When I power ON my T4-1, I got a prompt -> where I have to start /SYS and start /SP/console. How can I auto supply these two commands ?

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)