12-02-2009
Quote:
Originally Posted by
djehresmann
Are rc scripts executed serially or all at the same time.
RC scripts are launched serially but those staying alive (the daemons launched) are eventually running in parallel. SMF services on the other hand are launched in parallel as soon as dependencies are met.
Quote:
Is there a way to see this happen?
Rc scripts are launched by shell scripts (eg: /etc/rc3). You can easily instrument them by adding custom log commands (eg: "set -x", "echo $f" in the for loop). SMF methods launch can be displayed by adding the "-m verbose" flag to the boot command. You can also use dtrace if you are looking for detailed timings:
Minimal Solaris: Boot chart with help of DTrace and Python
10 More Discussions You Might Find Interesting
1. AIX
I understand that by putting in entries into the /etc/inittab file. We can actually call the our scripts during startup.
mkitab "start_server:2:once:sh /scripts/startserver.sh"
Would the system wait for startserver.sh finish executing before it goes to another entry? and how long would it... (1 Reply)
Discussion started by: vincente
1 Replies
2. SuSE
The wtmp file records all logins and logouts. Its format is exactly like utmp except that a null user name indicates a logout on the associated terminal. Furthermore, the terminal name "~" with user name "shutdown" or "reboot" indicates a system shutdown or reboot and the pair of terminal names... (1 Reply)
Discussion started by: Laksmi
1 Replies
3. Shell Programming and Scripting
Hi all,
I have a shell script which does db shutdown ..the script snippet which does this is as follows:
function call_sql_plus {
${SQLPLUS:-sqlplus} -s /nolog <<EOF
EXIT;
EOF
if
then
echo "Error occurred while calling sqlplus "
... (3 Replies)
Discussion started by: KrishnaSaran
3 Replies
4. UNIX for Dummies Questions & Answers
Having difficulty trying to locate startup and shutdown messages. I had a bunch of servers shutdown over the weekend (due to a scheduled power outage) and upon reboot a lot of the filesystems weren't mounted and several processes weren't started...
I checked /var/adm/messages and can't locate... (2 Replies)
Discussion started by: jamie_collins
2 Replies
5. AIX
hi,
If we place Sxx (startup script) and Kxx(shutdown script) in /etc/rc.d/rc2.d,then it would start and stop automatically(assume they are linked to other script that actually starts/stops).
is there really a link needed here to /etc/rc.d/init.d? if not,what is the use of this directory..?... (1 Reply)
Discussion started by: to_bsr
1 Replies
6. UNIX for Advanced & Expert Users
Hi All,
I want to shutdown the server if no one is actualy using it. Its a linux server.
I thought of sending a msg on users terminal for those who all are logged in and expecting a input from them.
If they will reply system should not get shutdown else it should not.
Can any one... (2 Replies)
Discussion started by: Sadhana
2 Replies
7. Shell Programming and Scripting
Dear Experts ,
I want to stop and Start tomcat at the time of shutdown and startup of our server . I was trying to stop tomcat with following command
# su - dm -c "/export/home/Finder/FinderWeb/jakarta-tomcat-3.3.1a/bin/shutdown.sh"
but i am getting following error. Please suggest .... (1 Reply)
Discussion started by: Amit.saini333
1 Replies
8. AIX
Hi All,
I would like to schedule auto IPL (shutdown and start-up) by using a shell script.
Can you please give me some idea?
want to test on my lab box first.
shell script should bring AIX LPAR down and then need to start/activate the LPAR after 30 min
any idea is highly... (3 Replies)
Discussion started by: System Admin 77
3 Replies
9. Shell Programming and Scripting
Hi all,
I'm writing a script to stop & start oracle:
su - oracle -c "sqlplus / as sysdba" -c "shutdown immediate">> ${log} 2>&1
The {log} refers to the log file. The part in bold gives error:
/usr/sbin/shutdown: Only root can run /usr/sbin/shutdown
Pls suggest how to correct this.
... (5 Replies)
Discussion started by: frum
5 Replies
10. UNIX for Beginners Questions & Answers
This question is more in the line of how init messages get sent to a console during startup/shutdown. My problem has to do with exporting a VM from AWS to KVM (and a retry on virtual box). I am looking for a understanding on how init messages are sent to a device and what controls them My two... (0 Replies)
Discussion started by: jtkells
0 Replies
init.d(4) init.d(4)
NAME
init.d - initialization and termination scripts for changing init states
SYNOPSIS
/etc/init.d
/etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appro-
priate to files in the rc?.d directories, where `?' is a single character corresponding to the init state. See init(1M) for definitions of
the states.
The service management facility (see smf(5)) is the preferred mechanism for service initiation and termination. The init.d and rc?.d direc-
tories are obsolete, and are provided for compatibility purposes only. Applications launched from these directories by svc.startd(1M) are
incomplete services, and will not be restarted on failure.
File names in rc?.d directories are of the form [SK]nn<init.d filename>, where S means start this job, K means kill this job, and nn is the
relative sequence number for killing or starting the job.
When entering a state (init S,0,2,3,etc.) the rc[S0-6] script executes those scripts in /etc/rc[S0-6].d that are prefixed with K followed
by those scripts prefixed with S. When executing each script in one of the /etc/rc[S0-6] directories, the /sbin/rc[S0-6] script passes a
single argument. It passes the argument 'stop' for scripts prefixed with K and the argument 'start' for scripts prefixed with S. There is
no harm in applying the same sequence number to multiple scripts. In this case the order of execution is deterministic but unspecified.
Guidelines for selecting sequence numbers are provided in README files located in the directory associated with that target state. For
example, /etc/rc[S0-6].d/README. Absence of a README file indicates that there are currently no established guidelines.
Do not put /etc/init.d in your $PATH. Having this directory in your $PATH can cause unexpected behavior. The programs in /etc/init.d are
associated with init state changes and, under normal circumstances, are not intended to be invoked from a command line.
Example 1: Example of /sbin/rc2.
When changing to init state 2 (multi-user mode, network resources not exported), /sbin/rc2 is initiated by the svc.startd(1M) process. The
following steps are performed by /sbin/rc2.
1. In the directory /etc/rc2.d are files used to stop processes that should not be running in state 2. The filenames are prefixed with K.
Each K file in the directory is executed (by /sbin/rc2) in alphanumeric order when the system enters init state 2. See example below.
2. Also in the rc2.d directory are files used to start processes that should be running in state 2. As in Step 1, each S file is executed.
Assume the file /etc/init.d/netdaemon is a script that will initiate networking daemons when given the argument 'start', and will terminate
the daemons if given the argument 'stop'. It is linked to /etc/rc2.d/S68netdaemon, and to /etc/rc0.d/K67netdaemon. The file is executed by
/etc/rc2.d/S68netdaemon start when init state 2 is entered and by /etc/rc0.d/K67netdaemon stop when shutting the system down.
svcs(1), init(1M), svc.startd(1M), svccfg(1M), smf(5)
Solaris now provides an expanded mechanism, which includes automated restart, for applications historically started via the init script
mechanism. The Service Management Facility (introduced in smf(5)) is the preferred delivery mechanism for persistently running applica-
tions. Existing init.d scripts will, however, continue to be executed according to the rules in this manual page. The details of execution
in relation to managed services are available in svc.startd(1M).
On earlier Solaris releases, a script named with a suffix of '.sh' would be sourced, allowing scripts to modify the environment of other
scripts executed later. This behavior is no longer supported; for altering the environment in which services are run, see the setenv sub-
command in svccfg(1M).
/sbin/rc2 has references to the obsolescent rc.d directory. These references are for compatibility with old INSTALL scripts. New INSTALL
scripts should use the init.d directory for related executables. The same is true for the shutdown.d directory.
17 Aug 2005 init.d(4)