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

Starting and Stopping Subsystems

Page 40 highlights

Managing Processes PIPE ALRM TERM USR1 USR2 CHLD PWR VTALRM PROF POLL WINCH STOP TSTP CONT TTIN TTOU URG LOST CPU FSZ For the shell built-in command: # kill -l 1) HUP 2) INT 3) QUIT 4) ILL 5) TRAP 6) IOT 7) EMT 8) FPE 9) KILL 10) BUS 11) SEGV 12) SYS 13) PIPE 14) ALRM 15) TERM 16) USR1 17) USR2 18) CHLD 19) PWR 20) VTALRM 21) PROF 22) POLL 23) WINCH 24) STOP 25) TSTP 26) CONT 27) TTIN 28) TTOU 29) URG 30) LOST 31) bad trap 32) bad trap 33) XCPU 34) XFSZ The HP-UX killall command is a procedure used by /etc/shutdown to kill all active processes not directly related to the shutdown procedure. killall is used chiefly to terminate all processes with open files so mounted file systems are no longer busy and can be unmounted. Starting and Stopping Subsystems The new system startup and shutdown paradigm introduced with HP-UX 10 allows command-line control of subsystems. A subsystem, in this sense, is a group of related processes and procedures. Subsystems can be controlled via the startup scripts found in /sbin/init.d. For example, the /sbin/init.d/nfs.client script controls daemons like biods and issues the appropriate mount or umount commands. To start this subsystem, on the command line type: # /sbin/init.d/nfs.client start To stop this subsystem, type: # /sbin/init.d/nfs.client stop What happens at this point also depends on what values are configured in the configuration script /etc/rc.config.d/nfsconf. All subsystems have a script in /sbin/init.d that can be used to start or stop the subsystem, and each has a configuration script in /etc/rc.config.d that governs precisely what happens when the former executes. For more information, see Chapter 2, "System Startup and Shutdown." Just remember that once a subsystem has been configured, it can easily be stopped or started on the command line with the following syntax: # /sbin/init.d/ subsystem_name start or 35

  • 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

Managing Processes
35
PIPE
ALRM
TERM
USR1
USR2
CHLD
PWR
VTALRM
PROF
POLL
WINCH
STOP
TSTP
CONT
TTIN
TTOU
URG
LOST
CPU
FSZ
For the shell built-in command:
# kill -l
1) HUP
8) FPE
15) TERM
22) POLL
29) URG
2) INT
9) KILL
16) USR1
23) WINCH 30) LOST
3) QUIT
10) BUS
17) USR2
24) STOP
31) bad trap
4) ILL
11) SEGV
18) CHLD
25) TSTP
32) bad trap
5) TRAP
12) SYS
19) PWR
26) CONT
33) XCPU
6) IOT
13) PIPE
20) VTALRM 27) TTIN
34) XFSZ
7) EMT
14) ALRM
21) PROF
28) TTOU
The HP-UX
killall
command is a procedure used by
/etc/shutdown
to kill all active processes not directly
related to the shutdown procedure.
killall
is used chiefly to terminate all processes with open files so
mounted file systems are no longer busy and can be unmounted.
Starting and Stopping Subsystems
The new system startup and shutdown paradigm introduced with HP-UX 10 allows command-line control
of subsystems. A subsystem, in this sense, is a group of related processes and procedures. Subsystems can
be controlled via the startup scripts found in
/sbin/init.d
. For example, the
/sbin/init.d/nfs.client
script
controls daemons like
biods
and issues the appropriate
mount
or
umount
commands. To start this
subsystem, on the command line type:
# /sbin/init.d/nfs.client start
To stop this subsystem, type:
# /sbin/init.d/nfs.client stop
What happens at this point also depends on what values are configured in the configuration script
/etc/rc.config.d/nfsconf
. All subsystems have a script in
/sbin/init.d
that can be used to start or stop the
subsystem, and each has a configuration script in
/etc/rc.config.d
that governs precisely what happens
when the former executes.
For more information, see Chapter 2, ²System Startup and Shutdown.³ Just
remember that once a subsystem has been configured, it can easily be stopped or started on the command
line with the following syntax:
# /sbin/init.d/ subsystem_name start
or