Commit Graph

9 Commits

Author SHA1 Message Date
tron 634457e76e Print out a message explaining why the system is rebooting if the root
filesystem is modified by fsck(8).
2008-03-02 21:31:30 +00:00
christos 3a24c02f26 cleanup fsck error handling:
1. explain what each error means
2. remove 130 (128 + 2) which was presumably there because fsck_msdos did
   not handle SIGINT properly
2008-02-24 01:05:35 +00:00
apb 31edfc6f0f * Add a stop_boot() function in rc.subr, to terminate a multi-user boot
by killing the parent process.  The parent's PID is saved in $RC_PID.
* In all rc.d/* scripts that previously tried to stop the boot,
  replace in-line code with "stop_boot".
* Document this.

This should fix PR 29822.
2007-04-06 14:20:08 +00:00
riz 7338f92d29 Trap SIGINT so that if fsck is interrupted by ^C, we drop into single-user
mode.  Fixes misc/29822 from der Mouse, fix from Arnaud Lacombe with
comment rework by me.
2006-10-07 04:11:23 +00:00
mycroft 7d2e1537c5 Add an _rc_subr_loaded variable, set to ":" by rc.subr. Scripts can use this
for a speedup by doing:
$_rc_subr_loaded . /etc/rc.subr
2004-08-13 18:08:03 +00:00
christos b5aee30a01 set fsck_flags=-p in /etc/defaults/rc.conf instead of checking if it is
empty in /etc/rc.d/fsck. From Bernd Ernesti.
2003-10-20 15:02:15 +00:00
christos e2ba1d7082 Allow overrides via fsck_flags 2003-10-15 17:38:04 +00:00
lukem f27a0c8f42 Now that "fsck -p" skips file systems that are mounted read-write,
always perform the disk check (unless /fastboot exists).  Previously
this would only occur when booting directly to multi-user, so the
fsck wouldn't happen after a single user boot going into multi-user.
2001-06-18 06:42:35 +00:00
lukem e26f093e93 convert fsck.sh -> fsck (using kill -TERM $$ to stop autoboot). 2000-08-21 23:38:07 +00:00