HP Visualize J210XC IRIX to HP-UX Migration Guide - Page 11

Startup

Page 11 highlights

System Startup and Shutdown Startup Beginning with HP-UX 10, /etc/inittab calls /sbin/rc, which in turn calls execution scripts to start subsystems. This approach follows the OSF/1 industry standard and has been adopted by Sun, SGI, and other vendors. There are four components to this method of startup and shutdown: • /sbin/rc • execution scripts • configuration variable scripts • link files /sbin/rc This script invokes execution scripts based on run levels. It is also known as the startup and shutdown sequencer script. Execution scripts These scripts start up and shut down various subsystems and are found in the /sbin/init.d directory. /sbin/rc invokes each execution script with one of four arguments, indicating the "mode": start Bring the subsystem up start_msg Report what the start action will do stop Bring the subsystem down stop_msg Report what the stop action will do These scripts are designed to never be modified. Instead, they are customized by sourcing in configuration files found in the /etc/rc.config.d directory. These configuration files contain variables that you can set. For example, in the configuration file /etc/rc.config.d/netconf, you can specify routing tables by setting the variables as follows: ROUTE_DESTINATION[0]="default" ROUTE_GATEWAY[0]="gateway_address" ROUTE_COUNT[0]="1" The execution script /sbin/init.d/net sources these and other network-related variables when it runs upon system startup. Configuration files are described further below. Upon startup, a checklist similar to the one below will appear based upon the exit value of each of the execution scripts. HP-UX Startup in progress Mount file systems OK ] Setting hostname OK ] Set privilege group OK ] Display date FAIL]* Enable auxiliary swap space N/A ] Start syncer daemon OK ] Configure LAN interfaces OK ] Start Software Distributor agent daemon.........[ OK ] The execution scripts have the following exit values: 0 Script exited without error. Causes the status OK to appear in the checklist. 1 Script encountered errors. Causes the status FAIL to appear in the checklist. 6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125

System Startup and Shutdown
6
Startup
Beginning with HP-UX 10,
/etc/inittab
calls
/sbin/rc
, which in turn calls execution scripts to start
subsystems. This approach follows the OSF/1 industry standard and has been adopted by Sun, SGI, and
other vendors. There are four components to this method of startup and shutdown:
/sbin/rc
execution scripts
configuration variable scripts
link files
/sbin/rc
This script invokes execution scripts based on run levels. It is also known as the startup and shutdown
sequencer script.
Execution scripts
These scripts start up and shut down various subsystems and are found in the
/sbin/init.d
directory.
/sbin/rc
invokes each execution script with one of four arguments, indicating the ²mode³:
start
Bring the subsystem up
start_msg
Report what the start action will do
stop
Bring the subsystem down
stop_msg
Report what the stop action will do
These scripts are designed to never be modified. Instead, they are customized by sourcing in configuration
files found in the
/etc/rc.config.d
directory. These configuration files contain variables that you can set. For
example, in the configuration file
/etc/rc.config.d/netconf,
you can specify routing tables by setting the
variables as follows:
ROUTE_DESTINATION[0]="default"
ROUTE_GATEWAY[0]="gateway_address"
ROUTE_COUNT[0]="1"
The execution script
/sbin/init.d/net
sources these and other network-related variables when it runs upon
system startup. Configuration files are described further below.
Upon startup, a checklist similar to the one below will appear based upon the exit value of each of the
execution scripts.
HP-UX Startup in progress
-----------------------------------
Mount file systems
..............................
[ OK ]
Setting hostname
................................
[ OK ]
Set privilege group
.............................
[ OK ]
Display date
...................................
[FAIL]*
Enable auxiliary swap space
....................
[ N/A ]
Start syncer daemon
.............................
[ OK ]
Configure LAN interfaces
........................
[ OK ]
Start Software Distributor agent daemon
.........
[ OK ]
The execution scripts have the following exit values:
0
Script exited without error. Causes the status
OK
to appear in the checklist.
1
Script encountered errors. Causes the status
FAIL
to appear in the checklist.