>On /sbin/rc2.d I found S910oracle linked to oracle in
>/sbin/init.d but on /sbin/rc3.d was nothing that I could relate to Oracle.
>
>How this works? Do I have to create the file in
>/sbin/init.d and link it to /sbin/rc2.d?
at run level 2 when the system is booting it looks sequentialy for files to start and
called S0XXXfile and gives the start option
at level 1 when system i beeing brought down
It look for Kxxxfile and give stop argument
I believe your oracle file should be in rc2.d for Kxxx and rc3 for SYYY
But its up to you...
Here is an example of what we do for start/stop scripts for oracle:
#!/usr/bin/ksh
export ORACTI_EXPLOIT=/opt/oracle/admin/exploit
export PATH=$PATH:/usr/bin:$ORACTI_EXPLOIT/proc
case "$1" in
start_msg)
echo "Start Oracle"
;;
stop_msg)
echo "Stop Oracle"
;;
start)
$ORACTI_EXPLOIT/proc/db_start
su - oracle -c $ORACTI_EXPLOIT/proc/net_start
;;
stop)
su - oracle -c $ORACTI_EXPLOIT/proc/net_stop
$ORACTI_EXPLOIT/proc/db_shut
;;
*)
echo "usage: $0 {start|stop}"
#rval=1
;;
esac
----------------------------------------
Here is an extract of a cronfile the way I do...
Notice I put conrfiles in a structure /sm/cron with big comments on the syntax
and usage since I have poor memory...
This leaves a way to modify the the cronfile by getting it at its location.
TO load it is simply crontab cronfile.root
--------------------------------------
# /sm/cron/cronfile.root
# crontab file for the super-user.
#
# ==========================================================================
# F O R M A T
# ==========================================================================
# Minute Hour Month_Day Month Weekday Command
# (0-59) (0-23) (1-31) (1-12) (0-6)*0=sun run-string
# * = in any crontab field represents all legal values.
# Therefore, to schedule the ps(1) cmd to execute at 5:10pm on every
# friday and monday during june, july, august, you would make an entry
# in your crontab fithe that looks like this :
# 10 17 * 6,7,8 1,5 ps>>psfile 2>&1
# The 2>&1 redirects any error msg to the file psfile.
# ==========================================================================
# archive annuelle de l export le 3 dimanche de janvier chaque annee
#00 04 * 1 0 /sm/bin/archive_annuelle >>/sm/log/archive_ann.er 2>&1
# log kernel diagnostic messages every 10 minutes
05,15,25,35,45,55 * * * * /usr/sbin/dmesg - >>/var/adm/messages
#05,15,20,35,45,55 * * * * /usr/bin/ulimit >>/var/adm/ulimit.cron 2>&1
#05,15,21,35,45,55 * * * * /usr/bin/ulimit -a >>/var/adm/ulimit.cron 2>&1
07,17,27,37,47,57 * * * * /var/adm/root/clean_tmp>>/var/adm/cleantmp.log 2>&1
# Sample nightly invocation of calendar. If you wish to run calendar,
# just uncomment the next line.
#0 4 * * * exec /usr/bin/calendar -
# ==========================================================================
# effacer les disques temporaires
# ==========================================================================
#
00 23 * * 1,2,3,4,5 /sm/cron/bin/effacer>>/sm/cron/log/efface.log 2>&1
05 23 * * 1,2,3,4,5 /sm/cron/bin/clean_xprt_s>/sm/cron/log/cleanXs.log 2>&1
# ============================ E N D =======================================
NOw user who are allowed to use cron or at cmd ar defined in files in /var/adm/cron:
-r--r--r-- 1 bin bin 18 Nov 14 2000 at.allow
-r--r--r-- 1 bin bin 31 Feb 12 2003 cron.allow
-rw-r--r-- 1 root root 1041016 May 18 10:47 log
in cron .allow and at.allow you give the users you are allowed:
:/var/adm/cron $ more cron.allow
root
adm
vbe
uucp
prod
rdm
dupont
-----
Courage!!
All the best
Victor
