1 .\" Copyright (c) 1980, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Portions of this manual page are Copyrighted by
5 .\" The NetBSD Foundation.
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
15 .\" 3. All advertising materials mentioning features or use of this software
16 .\" must display the following acknowledgement:
17 .\" This product includes software developed by the University of
18 .\" California, Berkeley and its contributors.
19 .\" 4. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
35 .\" @(#)rc.8 8.2 (Berkeley) 12/11/93
43 .Nd command scripts for auto-reboot and daemon startup
57 utility is the command script which controls the automatic boot process
62 script contains commands which are pertinent only
65 .Pa /usr/local/etc/rc.d/
66 mechanism is used instead of
71 it is still supported.
72 In this case, it should source
74 and contain additional custom startup code for your system.
75 The best way to handle
77 however, is to separate it out into
79 style scripts and place them under
80 .Pa /usr/local/etc/rc.d/ .
83 file contains the global system configuration information referenced
84 by the startup scripts, while
86 contains the local system configuration.
93 directories contain scripts which will be automatically
94 executed at boot time and shutdown time.
96 The sysrc(8) command provides a scripting interface to modify system
102 .Va autoboot Ns = Ns Li yes
104 .Pq Va rc_fast Ns = Ns Li yes ,
107 scripts from performing the check for already running processes
108 (thus speeding up the boot process).
110 .Va rc_fast Ns = Ns Li yes
111 speedup will not occur when
113 is started up after exiting the single-user shell.
115 Determine whether the system is booting diskless,
117 .Pa /etc/rc.initdiskless
124 shell functions to use.
126 Load the configuration files.
128 Determine if booting in a jail,
131 (no jails allowed) or
133 (only allow vnet-enabled jails) to the list of KEYWORDS to skip in
137 .Va ${firstboot_sentinel}
140 to the list of KEYWORDS to skip in
145 to order the files in
154 Call each script in turn using
162 and sources the script in a subshell.
165 suffix then it is sourced directly into the current shell.
166 Stop processing when the script that is the value of the
167 .Va $early_late_divider
170 Check again to see if the file
171 .Va ${firstboot_sentinel}
172 exists (in case it is located on a newly mounted file system)
173 and adjust the list of KEYWORDs to skip appropriately.
177 this time including the scripts in the
180 Ignore everything up to the
181 .Va $early_late_divider ,
182 then start executing the scripts as described above.
185 .Va ${firstboot_sentinel}
188 .Va ${firstboot_sentinel}-reboot
189 also exists (because it was created by a script), then delete it and reboot.
191 .Ss Operation of Nm rc.shutdown
198 shell functions to use.
200 Load the configuration files.
204 to order the files in
215 reverse that order, and assign the result to a variable.
217 Call each script in turn using
225 and sources the script in a subshell.
228 suffix then it is sourced directly into the current shell.
230 .Ss Contents of Nm rc.d/
234 The following file naming conventions are currently used in
236 .Bl -tag -width ".Pa ALLUPPERCASE" -offset indent
240 to ensure that certain operations are performed before others.
241 In order of startup, these are:
242 .Bl -tag -width ".Pa NETWORKING"
244 Ensure basic network services are running, including general
245 network configuration.
247 Ensure basic services
248 exist for services that start early (such as
250 because they are required by
254 Check-point before all general purpose daemons such as
259 Check-point before user login services
263 as well as services which might run commands as users
269 Scripts that are to be sourced into the current shell rather than a subshell
273 Extreme care must be taken in using this, as the startup sequence will
274 terminate if the script does.
276 Scripts that are sourced in a subshell.
277 The boot does not stop if such a script terminates with a non-zero status,
278 but a script can stop the boot if necessary by invoking the
284 Each script should contain
286 keywords, especially an appropriate
288 entry, and if necessary
294 Each script is expected to support at least the following arguments, which
295 are automatically supported if it uses the
298 .Bl -tag -width ".Cm restart" -offset indent
301 This should check that the service is to be started as specified by
303 Also checks if the service is already running and refuses to start if
305 This latter check is not performed by standard
307 scripts if the system is starting directly to multi-user mode, to
308 speed up the boot process.
313 check and start anyway.
315 If the service is to be started as specified by
318 This should check that the service is running and complain if it is not.
323 check and attempt to stop.
330 If the script starts a process (rather than performing a one-off
331 operation), show the status of the process.
332 Otherwise it is not necessary to support this argument.
333 Defaults to displaying the process ID of the program (if running).
335 If the script starts a process (rather than performing a one-off
336 operation), wait for the command to exit.
337 Otherwise it is not necessary to support this argument.
339 Return 0 if the service is enabled and 1 if it is not.
340 This command does not print anything.
344 variables are used to control the startup of the service (if any).
347 If a script must implement additional commands it can list them in
350 variable, and define their actions in a variable constructed from
351 the command name (see the
355 The following key points apply to old-style scripts in
356 .Pa /usr/local/etc/rc.d/ :
359 Scripts are only executed if their
361 matches the shell globbing pattern
363 and they are executable.
364 Any other files or directories present within the directory are silently
367 When a script is executed at boot time, it is passed the string
369 as its first and only argument.
370 At shutdown time, it is passed the string
372 as its first and only argument.
375 scripts are expected to handle these arguments appropriately.
376 If no action needs to be taken at a given time
377 (either boot time or shutdown time),
378 the script should exit successfully and without producing an error message.
380 The scripts within each directory are executed in lexicographical order.
381 If a specific order is required,
382 numbers may be used as a prefix to the existing filenames,
385 would be executed before
387 without the numeric prefixes the opposite would be true.
389 The output from each script is traditionally a space character,
390 followed by the name of the software package being started or shut down,
392 a trailing newline character (see the
396 .Sh SCRIPTS OF INTEREST
397 When an automatic reboot is in progress,
399 is invoked with the argument
401 One of the scripts run from
413 all the disks of minor inconsistencies resulting
414 from the last system shutdown.
415 If this fails, then checks/repairs of serious inconsistencies
416 caused by hardware or software failure will be performed
417 in the background at the end of the booting process.
420 is not set, when going from single-user to multi-user mode for example,
421 the script does not do anything.
425 script can execute scripts from multiple
428 The default location includes
429 .Pa /usr/local/etc/rc.d/ ,
430 but these may be overridden with the
437 script is used to set any special configurations for serial devices.
441 script is used to configure rules for the kernel based firewall
443 It has several possible options:
445 .Bl -tag -width ".Ar filename" -compact -offset indent
449 will try to protect just this machine
451 will try to protect a whole network
453 totally disables IP services except via
457 disables the loading of firewall rules
459 will load the rules in the given filename (full path required).
464 scripts are used to configure ATM network interfaces.
465 The interfaces are configured in three passes.
466 The first pass performs the initial interface configuration.
467 The second pass completes the interface configuration and defines PVCs and
468 permanent ATMARP entries.
469 The third pass starts any ATM daemons.
471 Most daemons, including network related daemons, have their own script in
473 which can be used to start, stop, and check the status of the service.
475 Any architecture specific scripts, such as
477 for example, specifically check that they are on that architecture
478 before starting the daemon.
480 Following tradition, all startup files reside in
483 .Bl -tag -compact -width Pa
486 .It Pa /etc/rc.conf.local
488 .It Pa /etc/rc.firewall
490 .It Pa /etc/rc.shutdown
492 .It Pa /var/run/dmesg.boot
494 results soon after the
499 buffer in the kernel no longer has this information.
502 The following is a minimal
505 Most scripts require little more than the following.
506 .Bd -literal -offset indent
511 # REQUIRE: bar_service_required_to_precede_foo
517 command="/usr/local/bin/foo"
523 Certain scripts may want to provide enhanced functionality.
524 The user may access this functionality through additional commands.
525 The script may list and define as many commands at it needs.
526 .Bd -literal -offset indent
531 # REQUIRE: bar_service_required_to_precede_foo
532 # BEFORE: baz_service_requiring_foo_to_precede_it
538 command="/usr/local/bin/foo"
539 extra_commands="nop hello"
540 hello_cmd="echo Hello World."
552 As all processes are killed by
554 at shutdown, the explicit
556 is unnecessary, but is often included.