freebsd-dev/etc/rc

80 lines
2.6 KiB
Plaintext
Raw Normal View History

#!/bin/sh
#
# Copyright (c) 2000-2004 The FreeBSD Project
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
#
# @(#)rc 5.27 (Berkeley) 6/5/91
1999-08-27 23:37:10 +00:00
# $FreeBSD$
#
# System startup script run by init on autoboot
# or after single-user.
# Output and error are redirected to console by init,
# and the console is the controlling terminal.
# Note that almost all of the user-configurable behavior is no longer in
# this file, but rather in /etc/defaults/rc.conf. Please check that file
# first before contemplating any changes here. If you do need to change
# this file for some reason, we would like to know about it.
stty status '^T'
# Set shell to ignore SIGINT (2), but not children;
# shell catches SIGQUIT (3) and returns to single user.
#
trap : 2
trap "echo 'Boot interrupted'; exit 1" 3
HOME=/
PATH=/sbin:/bin:/usr/sbin:/usr/bin
export HOME PATH
. /etc/rc.subr
# Note: the system configuration files are loaded as part of
# the RCNG system (rc.d/rccond). Do not load them here as it may
# interfere with diskless booting.
This is the rc work as provided by pts, I will me makeing some additional changes to it based upon other outstanding bug reports and commits made after his work. Comments: (a) sysconfig is still used to do all configuration. I was not going to change that out from under you.... a user never need edit netstart or rc* unless they're being very weird. (b) rc.maint has been folded back into rc. It is just unworkable as a separate chunk because of ordering bogosities (c) netstart does what it says... it starts up enough of the network to get up, it doesn't start every bloody daemon that might talk to a socket... netstart ifconfig's the devices and sets up routing if configured to do so. (d) nfs disks are mounted immediately after netstart completes (e) syslog is started as early as possible (right after nfs) so that error messages can get logged to remote syslog servers properly (f) named is started (there is an argument that says that named should be started before syslogd because if you are the dns server for your domain, you'd like named to resolve remote hosts in syslog.conf, but this is a minority case and the trivial workarround is to put the syslog host in /etc/hosts or use an /etc/resolv.conf -- why? because you want syslog to catch named errors, which is a MUCH more important and likely occurance) (g) NOW all of the rest of the network daemons such as the time stuff, RPC, NIS, NFS, Kerberos and inetd are started (h) the rest of the generic stuff is done (cron/printer/sendmail) (i) shared libraries are set (j) /etc/rc.i386 is run (this does FreeBSD/386 specific stuff like ibcs2, xtend, and all of the syscons stuff (this is actually started as /etc/rc.`uname -m` (k) the syscons stuff has gotten a serious cleaning to make it consistent with rc conventions (l) rc.local has had the comments about syscons removed (they are not relevant to this file now) and the full name of the kernel has been restored to /etc/motd Submitted by: pts
1995-03-30 06:26:19 +00:00
#
if [ "$1" = autoboot ]; then
autoboot=yes
_boot="faststart"
rc_fast=yes # run_rc_command(): do fast booting
else
autoboot=no
_boot="start"
fi
os=`eval ${CMD_OSTYPE}`
skip="-s nostart"
[ `/sbin/sysctl -n security.jail.jailed` -eq 1 ] && skip="$skip -s nojail"
files=`rcorder -k ${os} ${skip} /etc/rc.d/* 2>/dev/null`
for _rc_elem in ${files}; do
run_rc_script ${_rc_elem} ${_boot}
done
Update the fsck command in /etc/rc to use the new background fsck checking. Applying these changes (typically via mergemaster) will cause your system to start running background checks on all your soft update enabled filesystems (provided that you have a kernel with the required functionality, e.g., one built since the end of April). Please report any and all problems to mckusick@mckusick.com (not mckusick@freebsd.org which I read infrequently). See the comment above the fsck command in /etc/rc for instructions on how to disable background checking should it cause you too much trouble. Several FAQs: 1) Can I reboot before the background checks are done? Ans) Yes, when the system restarts the checks will pick up where they left off. 2) Can a crash during checking corrupt my filesystem? Ans) No, recovered resources are returned to the system using soft updates which ensure that the freeing is done in a safe order. 3) How will I know if any background checks are being done? Ans) Filesystems that are to be checked in background will be listed as `DEFER FOR BACKGROUND CHECKING' at the usual fsck check time during system startup. 4) What happens to the output of the background checks? Ans) It is sent to syslog `daemon' facility log level `notice'. 5) When will this feature be available in the 4.X kernel? Ans) Never. It is much too radical and extensive a change to be MFC'ed. Besides, it needs many months of experience and tuning before it is ready for widespread use. 6) What happens if a background fsck fails (i.e., fsck finds errors that would normally require a manual fsck)? Ans) The filesystem will be marked as needing a manual fsck. At the next system reboot, the check will be done in foreground and the usual actions taken (usually a failure to go multi-user until fsck has been run by hand on the affected filesystem).
2001-05-11 07:40:39 +00:00
echo ''
date
exit 0