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. Neither the name of the University nor the names of its contributors
16 .\" may be used to endorse or promote products derived from this software
17 .\" without specific prior written permission.
19 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
20 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
23 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
24 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
25 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
26 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
27 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
28 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
31 .\" @(#)rc.8 8.2 (Berkeley) 12/11/93
39 .Nd command scripts for auto-reboot and daemon startup
53 utility is the command script which controls the automatic boot process
58 script contains commands which are pertinent only
61 .Pa /usr/local/etc/rc.d/
62 mechanism is used instead of
67 it is still supported.
68 In this case, it should source
70 and contain additional custom startup code for your system.
71 The best way to handle
73 however, is to separate it out into
75 style scripts and place them under
76 .Pa /usr/local/etc/rc.d/ .
79 file contains the global system configuration information referenced
80 by the startup scripts, while
82 contains the local system configuration.
89 directories contain scripts which will be automatically
90 executed at boot time and shutdown time.
94 command provides a convenient interface to manage rc.d services.
98 command provides a scripting interface to modify system config files.
103 .Va autoboot Ns = Ns Li yes
105 .Pq Va rc_fast Ns = Ns Li yes ,
108 scripts from performing the check for already running processes
109 (thus speeding up the boot process).
111 .Va rc_fast Ns = Ns Li yes
112 speedup will not occur when
114 is started up after exiting the single-user shell.
116 Determine whether the system is booting diskless,
118 .Pa /etc/rc.initdiskless
125 shell functions to use.
127 Load the configuration files.
129 Determine if booting in a jail,
132 (no jails allowed) or
134 (only allow vnet-enabled jails) to the list of KEYWORDS to skip in
138 .Va ${firstboot_sentinel}
141 to the list of KEYWORDS to skip in
146 to order the files in
155 Call each script in turn using
163 and sources the script in a subshell.
164 Stop processing when the script that is the value of the
165 .Va $early_late_divider
168 Check again to see if the file
169 .Va ${firstboot_sentinel}
170 exists (in case it is located on a newly mounted file system)
171 and adjust the list of KEYWORDs to skip appropriately.
175 this time including the scripts in the
178 Ignore everything up to the
179 .Va $early_late_divider ,
180 then start executing the scripts as described above.
183 .Va ${firstboot_sentinel}
186 .Va ${firstboot_sentinel}-reboot
187 also exists (because it was created by a script), then delete it and reboot.
189 .Ss Operation of Nm rc.shutdown
196 shell functions to use.
198 Load the configuration files.
202 to order the files in
213 reverse that order, and assign the result to a variable.
215 Call each script in turn using
223 and sources the script in a subshell.
225 .Ss Contents of Nm rc.d/
229 The following file naming conventions are currently used in
231 .Bl -tag -width ".Pa ALLUPPERCASE" -offset indent
235 to ensure that certain operations are performed before others.
236 In order of startup, these are:
237 .Bl -tag -width ".Pa NETWORKING"
239 Ensure basic network services are running, including general
240 network configuration.
242 Ensure basic services
243 exist for services that start early (such as
245 because they are required by
249 Check-point before all general purpose daemons such as
254 Check-point before user login services
258 as well as services which might run commands as users
264 Scripts that are sourced in a subshell.
265 The boot does not stop if such a script terminates with a non-zero status,
266 but a script can stop the boot if necessary by invoking the
272 Each script should contain
274 keywords, especially an appropriate
276 entry, and if necessary
282 Each script is expected to support at least the following arguments, which
283 are automatically supported if it uses the
286 .Bl -tag -width ".Cm restart" -offset indent
289 This should check that the service is to be started as specified by
291 Also checks if the service is already running and refuses to start if
293 This latter check is not performed by standard
295 scripts if the system is starting directly to multi-user mode, to
296 speed up the boot process.
301 check and start anyway.
303 If the service is to be started as specified by
306 This should check that the service is running and complain if it is not.
311 check and attempt to stop.
318 If the script starts a process (rather than performing a one-off
319 operation), show the status of the process.
320 Otherwise it is not necessary to support this argument.
321 Defaults to displaying the process ID of the program (if running).
323 Enable the service in
326 Disable the service in
329 Remove the service from
332 .Ql Li service_delete_empty
335 .Pa /etc/rc.conf.d/$servicename
336 will be deleted if empty after modification.
338 Print a short description of what the script does.
340 Print the script's non-standard commands.
342 If the script starts a process (rather than performing a one-off
343 operation), wait for the command to exit.
344 Otherwise it is not necessary to support this argument.
346 Return 0 if the service is enabled and 1 if it is not.
347 This command does not print anything.
351 variables are used to control the startup of the service (if any).
354 If a script must implement additional commands it can list them in
357 variable, and define their actions in a variable constructed from
358 the command name (see the
362 The following key points apply to old-style scripts in
363 .Pa /usr/local/etc/rc.d/ :
366 Scripts are only executed if their
368 matches the shell globbing pattern
370 and they are executable.
371 Any other files or directories present within the directory are silently
374 When a script is executed at boot time, it is passed the string
376 as its first and only argument.
377 At shutdown time, it is passed the string
379 as its first and only argument.
382 scripts are expected to handle these arguments appropriately.
383 If no action needs to be taken at a given time
384 (either boot time or shutdown time),
385 the script should exit successfully and without producing an error message.
387 The scripts within each directory are executed in lexicographical order.
388 If a specific order is required,
389 numbers may be used as a prefix to the existing filenames,
392 would be executed before
394 without the numeric prefixes the opposite would be true.
396 The output from each script is traditionally a space character,
397 followed by the name of the software package being started or shut down,
399 a trailing newline character (see the
403 .Sh SCRIPTS OF INTEREST
404 When an automatic reboot is in progress,
406 is invoked with the argument
408 One of the scripts run from
420 all the disks of minor inconsistencies resulting
421 from the last system shutdown.
422 If this fails, then checks/repairs of serious inconsistencies
423 caused by hardware or software failure will be performed
424 in the background at the end of the booting process.
427 is not set, when going from single-user to multi-user mode for example,
428 the script does not do anything.
432 script can execute scripts from multiple
435 The default location includes
436 .Pa /usr/local/etc/rc.d/ ,
437 but these may be overridden with the
444 script is used to set any special configurations for serial devices.
448 script is used to configure rules for the kernel based firewall
450 It has several possible options:
452 .Bl -tag -width ".Ar filename" -compact -offset indent
456 will try to protect just this machine
458 will try to protect a whole network
460 totally disables IP services except via
464 disables the loading of firewall rules
466 will load the rules in the given filename (full path required).
469 Most daemons, including network related daemons, have their own script in
471 which can be used to start, stop, and check the status of the service.
473 Any architecture specific scripts, such as
475 for example, specifically check that they are on that architecture
476 before starting the daemon.
478 Following tradition, all startup files reside in
481 .Bl -tag -compact -width Pa
484 .It Pa /etc/rc.conf.local
486 .It Pa /etc/rc.firewall
488 .It Pa /etc/rc.shutdown
490 .It Pa /var/run/dmesg.boot
492 results soon after the
497 buffer in the kernel no longer has this information.
500 The following is a minimal
503 Most scripts require little more than the following.
504 .Bd -literal -offset indent
509 # REQUIRE: bar_service_required_to_precede_foo
515 command="/usr/local/bin/foo"
521 Certain scripts may want to provide enhanced functionality.
522 The user may access this functionality through additional commands.
523 The script may list and define as many commands at it needs.
524 .Bd -literal -offset indent
529 # REQUIRE: bar_service_required_to_precede_foo
530 # BEFORE: baz_service_requiring_foo_to_precede_it
536 command="/usr/local/bin/foo"
537 extra_commands="nop hello"
538 hello_cmd="echo Hello World."
550 As all processes are killed by
552 at shutdown, the explicit
554 is unnecessary, but is often included.