rc revision 1.169
1#!/bin/sh 2# 3# $NetBSD: rc,v 1.169 2014/07/27 07:46:46 apb Exp $ 4# 5# rc -- 6# Run the scripts in /etc/rc.d with rcorder, and log output 7# to /var/run/rc.log. 8 9# System startup script run by init(8) on autoboot or after single-user. 10# Output and error are redirected to console by init, and the console 11# is the controlling terminal. 12 13export HOME=/ 14export PATH=/sbin:/bin:/usr/sbin:/usr/bin 15umask 022 16 17if [ -e ./rc.subr ] ; then 18 . ./rc.subr # for testing 19else 20 . /etc/rc.subr 21fi 22. /etc/rc.conf 23_rc_conf_loaded=true 24 25: ${RC_LOG_FILE:="/var/run/rc.log"} 26 27# rc.subr redefines echo and printf. Undo that here. 28unset echo ; unalias echo 29unset printf ; unalias printf 30 31if ! checkyesno rc_configured; then 32 echo "/etc/rc.conf is not configured. Multiuser boot aborted." 33 exit 1 34fi 35 36if [ "$1" = autoboot ]; then 37 autoboot=yes 38 rc_fast=yes # run_rc_command(): do fast booting 39fi 40 41# 42# Completely ignore INT and QUIT at the outer level. The rc_real_work() 43# function should do something different. 44# 45trap '' INT QUIT 46 47# 48# This string will be used to mark lines of meta-data sent over the pipe 49# from the rc_real_work() function to the rc_postprocess() function. Lines 50# not so marked are assumed to be output from rc.d scripts. 51# 52# This string is long and unique to ensure that it does not accidentally 53# appear in output from any rc.d script. It must not contain any 54# characters that are special to glob expansion ('*', '?', '[', or ']'). 55# 56rc_metadata_prefix="$0:$$:metadata:"; 57 58# Child scripts may sometimes want to print directly to the original 59# stdout and stderr, bypassing the pipe to the postprocessor. These 60# _rc_*_fd variables are private, shared with /etc/rc.subr, but not 61# intended to be used directly by child scripts. (Child scripts 62# may use rc.subr's no_rc_postprocess function.) 63# 64_rc_original_stdout_fd=7; export _rc_original_stdout_fd 65_rc_original_stderr_fd=8; export _rc_original_stderr_fd 66eval "exec ${_rc_original_stdout_fd}>&1" 67eval "exec ${_rc_original_stderr_fd}>&2" 68 69# 70# rc_real_work 71# Do the real work. Output from this function will be piped into 72# rc_postprocess(), and some of the output will be marked as 73# metadata. 74# 75# The body of this function is defined using (...), not {...}, to force 76# it to run in a subshell. 77# 78rc_real_work() 79( 80 stty status '^T' 81 82 # print_rc_metadata() wants to be able to print to the pipe 83 # that goes to our postprocessor, even if its in a context 84 # with redirected output. 85 # 86 _rc_postprocessor_fd=9 ; export _rc_postprocessor_fd 87 _rc_pid=$$ ; export _rc_pid 88 eval "exec ${_rc_postprocessor_fd}>&1" 89 90 # Print a metadata line when we exit 91 # 92 trap 'es=$?; print_rc_metadata "exit:$es"; trap "" 0; exit $es' 0 93 94 # Set shell to ignore SIGINT, but children will not ignore it. 95 # Shell catches SIGQUIT and returns to single user. 96 # 97 trap : INT 98 trap '_msg="Boot interrupted at $(date)"; 99 print_rc_metadata "interrupted:${_msg}"; 100 exit 1' QUIT 101 102 print_rc_metadata "start:$(date)" 103 104 # 105 # The stop_boot() function in rc.subr may kill $RC_PID. We want 106 # it to kill the subshell running this rc_real_work() function, 107 # rather than killing the parent shell, because we want the 108 # rc_postprocess() function to be able to log the error 109 # without being killed itself. 110 # 111 # "$$" is the pid of the top-level shell, not the pid of the 112 # subshell that's executing this function. The command below 113 # tentatively assumes that the parent of the "/bin/sh -c ..." 114 # process will be the current subshell, and then uses "kill -0 115 # ..." to check the result. If the "/bin/sh -c ..." process 116 # fails, or returns the pid of an ephemeral process that exits 117 # before the "kill" command, then we fall back to using "$$". 118 # 119 RC_PID=$(/bin/sh -c 'ps -p $$ -o ppid=') || RC_PID=$$ 120 kill -0 $RC_PID >/dev/null 2>&1 || RC_PID=$$ 121 122 # 123 # As long as process $RC_PID is still running, send a "nop" 124 # metadata message to the postprocessor every few seconds. 125 # This should help flush partial lines that may appear when 126 # rc.d scripts that are NOT marked with "KEYWORD: interactive" 127 # nevertheless attempt to print prompts and wait for input. 128 # 129 ( 130 while kill -0 $RC_PID ; do 131 print_rc_metadata "nop" 132 sleep 3 133 done 134 ) & 135 136 # 137 # Get a list of all rc.d scripts, and use rcorder to choose 138 # what order to execute them. 139 # 140 # For testing, allow RC_FILES_OVERRIDE from the environment to 141 # override this. 142 # 143 print_rc_metadata "cmd-name:rcorder" 144 scripts=$(for rcd in ${rc_directories:-/etc/rc.d}; do 145 test -d ${rcd} && echo ${rcd}/*; 146 done) 147 files=$(rcorder -s nostart ${rc_rcorder_flags} ${scripts}) 148 print_rc_metadata "cmd-status:rcorder:$?" 149 150 if [ -n "${RC_FILES_OVERRIDE}" ]; then 151 files="${RC_FILES_OVERRIDE}" 152 fi 153 154 # 155 # Run the scripts in order. 156 # 157 for _rc_elem in $files; do 158 print_rc_metadata "cmd-name:$_rc_elem" 159 run_rc_script $_rc_elem start 160 print_rc_metadata "cmd-status:$_rc_elem:$?" 161 done 162 163 print_rc_metadata "end:$(date)" 164 exit 0 165) 166 167# 168# rc_postprocess 169# Post-process the output from the rc_real_work() function. For 170# each line of input, we have to decide whether to print the line 171# to the console, print a twiddle on the console, print a line to 172# the log, or some combination of these. 173# 174# If rc_silent is true, then suppress most output, instead running 175# rc_silent_cmd (typically "twiddle") for each line. 176# 177# The body of this function is defined using (...), not {...}, to force 178# it to run in a subshell. 179# 180# We have to deal with the following constraints: 181# 182# * There may be no writable file systems early in the boot, so 183# any use of temporary files would be problematic. 184# 185# * Scripts run during the boot may clear /tmp and/var/run, so even 186# if they are writable, using those directories too early may be 187# problematic. We assume that it's safe to write to our log file 188# after the mountcritlocal script has run. 189# 190# * /usr/bin/tee cannot be used because the /usr file system may not 191# be mounted early in the boot. 192# 193# * All calls to the rc_log_message and rc_log_flush functions must be 194# from the same subshell, otherwise the use of a shell variable to 195# buffer log messages will fail. 196# 197rc_postprocess() 198( 199 local line 200 local before after 201 local IFS='' 202 203 # Try quite hard to flush the log to disk when we exit. 204 trap 'es=$?; rc_log_flush FORCE; trap "" 0; exit $es' 0 205 206 yesno_to_truefalse rc_silent 2>/dev/null 207 208 while read -r line ; do 209 case "$line" in 210 "${rc_metadata_prefix}"*) 211 after="${line#*"${rc_metadata_prefix}"}" 212 rc_postprocess_metadata "${after}" 213 ;; 214 *"${rc_metadata_prefix}"*) 215 # magic string is present, but not at the start of 216 # the line. Treat it as a partial line of 217 # ordinary data, followed by a line of metadata. 218 before="${line%"${rc_metadata_prefix}"*}" 219 rc_postprocess_partial_line "${before}" 220 after="${line#*"${rc_metadata_prefix}"}" 221 rc_postprocess_metadata "${after}" 222 ;; 223 *) 224 rc_postprocess_plain_line "${line}" 225 ;; 226 esac 227 done 228 229 # If we get here, then the rc_real_work() function must have 230 # exited uncleanly. A clean exit would have been accompanied by 231 # a line of metadata that would have prevented us from getting 232 # here. 233 # 234 exit 1 235) 236 237# 238# rc_postprocess_plain_line string 239# $1 is a string representing a line of output from one of the 240# rc.d scripts. Append the line to the log, and also either 241# display the line on the console, or run $rc_silent_cmd, 242# depending on the value of $rc_silent. 243# 244rc_postprocess_plain_line() 245{ 246 local line="$1" 247 rc_log_message "${line}" 248 if $rc_silent; then 249 eval "$rc_silent_cmd" 250 else 251 printf "%s\n" "${line}" 252 fi 253} 254 255# 256# rc_postprocess_partial_line string 257# This is just like rc_postprocess_plain_line, except that 258# a newline is not appended to the string. 259# 260rc_postprocess_partial_line() 261{ 262 local line="$1" 263 rc_log_message_n "${line}" 264 if $rc_silent; then 265 eval "$rc_silent_cmd" 266 else 267 printf "%s" "${line}" 268 fi 269} 270 271# 272# rc_postprocess_metadata string 273# $1 is a string containing metadata from the rc_real_work() 274# function. The rc_metadata_prefix marker should already 275# have been removed before the string is passed to this function. 276# Take appropriate action depending on the content of the string. 277# 278rc_postprocess_metadata() 279{ 280 local metadata="$1" 281 local keyword args 282 local msg 283 local IFS=':' 284 285 # given metadata="bleep:foo bar:baz", 286 # set keyword="bleep", args="foo bar:baz", 287 # $1="foo bar", $2="baz" 288 # 289 keyword="${metadata%%:*}" 290 args="${metadata#*:}" 291 set -- $args 292 293 case "$keyword" in 294 start) 295 # Marks the start of the entire /etc/rc script. 296 # $args contains a date/time. 297 rc_log_message "[$0 starting at $args]" 298 if ! $rc_silent; then 299 printf "%s\n" "$args" 300 fi 301 ;; 302 cmd-name) 303 # Marks the start of a child script (usually one of 304 # the /etc/rc.d/* scripts). 305 rc_log_message "[running $1]" 306 ;; 307 cmd-status) 308 # Marks the end of a child script. 309 # $1 is a command name, $2 is the command's exit status. 310 # If the command failed, report it, and add it to a list. 311 if [ "$2" != 0 ]; then 312 rc_failures="${rc_failures}${rc_failures:+ }$1" 313 msg="$1 $(human_exit_code $2)" 314 rc_log_message "$msg" 315 if ! $rc_silent; then 316 printf "%s\n" "$msg" 317 fi 318 fi 319 # After the mountcritlocal script has finished, it's 320 # OK to flush the log to disk 321 case "$1" in 322 */mountcritlocal) 323 rc_log_flush OK 324 ;; 325 esac 326 ;; 327 nop) 328 # Do nothing. 329 # This has the side effect of flushing partial lines, 330 # and the echo() and printf() functions in rc.subr take 331 # advantage of this. 332 ;; 333 note) 334 # Unlike most metadata messages, which should be used 335 # only by /etc/rc and rc.subr, the "note" message may be 336 # used directly by /etc.rc.d/* and similar scripts. 337 # It adds a note to the log file, without displaying 338 # it to stdout. 339 rc_log_message "[NOTE: $args]" 340 ;; 341 end) 342 # Marks the end of processing, after the last child script. 343 # If any child scripts (or other commands) failed, report them. 344 # 345 if [ -n "$rc_failures" ]; then 346 rc_log_message "[failures]" 347 msg="The following components reported failures:" 348 msg="${msg}${nl}$( echo " ${rc_failures}" | fmt )" 349 msg="${msg}${nl}See ${RC_LOG_FILE} for more information." 350 rc_log_message "${msg}" 351 printf "%s\n" "${msg}" 352 fi 353 # 354 # Report the end date/time, even in silent mode 355 # 356 rc_log_message "[$0 finished at $args]" 357 printf "%s\n" "$args" 358 ;; 359 exit) 360 # Marks an exit from the rc_real_work() function. 361 # This may be a normal or abnormal exit. 362 # 363 rc_log_message "[$0 exiting with status $1]" 364 exit $1 365 ;; 366 interrupted) 367 # Marks an interrupt trapped by the rc_real_work() function. 368 # $args is a human-readable message. 369 rc_log_message "$args" 370 printf "%s\n" "$args" 371 ;; 372 *) 373 # an unrecognised line of metadata 374 rc_log_message "[metadata:${metadata}]" 375 ;; 376 esac 377} 378 379# 380# rc_log_message string [...] 381# Write a message to the log file, or buffer it for later. 382# This function appends a newline to the message. 383# 384rc_log_message() 385{ 386 _rc_log_buffer="${_rc_log_buffer}${*}${nl}" 387 rc_log_flush 388} 389 390# 391# rc_log_message_n string [...] 392# Just like rc_log_message, except without appending a newline. 393# 394rc_log_message_n() 395{ 396 _rc_log_buffer="${_rc_log_buffer}${*}" 397 rc_log_flush 398} 399 400# 401# rc_log_flush [OK|FORCE] 402# save outstanding messages from $_rc_log_buffer to $RC_LOG_FILE. 403# 404# The log file is expected to reside in the /var/run directory, which 405# may not be writable very early in the boot sequence, and which is 406# erased a little later in the boot sequence. We therefore avoid 407# writing to the file until we believe it's safe to do so. We also 408# assume that it's reasonable to always append to the file, never 409# truncating it. 410# 411# Optional argument $1 may be "OK" to report that writing to the log 412# file is expected to be safe from now on, or "FORCE" to force writing 413# to the log file even if it may be unsafe. 414# 415# Returns a non-zero status if messages could not be written to the 416# file. 417# 418rc_log_flush() 419{ 420 # 421 # If $_rc_log_flush_ok is false, then it's probably too early to 422 # write to the log file, so don't do it, unless $1 is "FORCE". 423 # 424 : ${_rc_log_flush_ok=false} 425 case "$1:$_rc_log_flush_ok" in 426 OK:*) 427 _rc_log_flush_ok=true 428 ;; 429 FORCE:*) 430 : OK just this once 431 ;; 432 *:true) 433 : OK 434 ;; 435 *) 436 # it's too early in the boot sequence, so don't flush 437 return 1 438 ;; 439 esac 440 441 # 442 # Now append the buffer to the file. The buffer should already 443 # contain a trailing newline, so don't add an extra newline. 444 # 445 if [ -n "$_rc_log_buffer" ]; then 446 if { printf "%s" "${_rc_log_buffer}" >>"${RC_LOG_FILE}" ; } \ 447 2>/dev/null 448 then 449 _rc_log_buffer="" 450 else 451 return 1 452 fi 453 fi 454 return 0 455} 456 457# 458# Most of the action is in the rc_real_work() and rc_postprocess() 459# functions. 460# 461rc_real_work "$@" 2>&1 | rc_postprocess 462exit $? 463