HP-UX HB v13.00 Ch-03 - System Startup

HP-UX Handbook – Rev 13.00 Page 11 (of 14)
Chapter 03 System Startup
October 29, 2013
be stopped in the reverse order to eliminate any dependencies between subsystems. This means
that kill scripts will generally not have the same numbers as their start script counterparts. E.g. if
two subsystems must be started in a given order due to dependencies (e.g., S111house followed
by S222uses_house), the kill counterparts to these scripts must be numbered so that the
subsystems are stopped in the opposite order in which they were started (e.g., K778uses_house
followed by K889house).
Run Level Definitions
When entering from lower state (run level), all start scripts are executed, and when entering from
higher states, all kill scripts are executed. This is applicable for run levels 1 through 6.
The following table shows a typical system startup.
Run level
State
Sequencer Dir
subsystems that are started
0
Halted
/sbin/rc0.d
/
S
Single User
/sbin/rc0.d
/
1
Minimal
/sbin/rc1.d
configure system for crash dump
mount local file systems
set hostname
enable secondary swap
start syncer
2
Multi-User
/sbin/rc2.d
configure unconfigured software
start syslog daemon
configure lan interfaces
startup network
start NFS client (mount NFS filesystem)
start cron
start Measureware daemon
3
Exported
/sbin/rc3.d
start NFS server (export NFS filesystems)
join ServiceGuard cluster if applicable
This is the default run level
4
CDE
/sbin/rc4.d
start graphical user interface
5
Not used
n/a
customer applications
6
Not used
n/a
customer applications