Date: Sat, 3 Jul 2004 06:50:22 GMT From: Craig Carey <snowfall@gmx.co.uk> To: freebsd-bugs@FreeBSD.org Subject: Re: conf/68525: Loader's verbose boot mode has rc.d/localdaemon not name local scripts Message-ID: <200407030650.i636oMPI003781@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/68525; it has been noted by GNATS.
From: Craig Carey <snowfall@gmx.co.uk>
To: freebsd-gnats-submit@FreeBSD.org, research@ijs.co.nz
Cc:
Subject: Re: conf/68525: Loader's verbose boot mode has
rc.d/localdaemon not name local scripts
Date: Sat, 03 Jul 2004 18:39:47 +1200
----
A repeat of the description of the issue (with lines now wrapped):
When FreeBSD 5.2 is booted with verbose logging enabled ("Boot FreeBSD
with verbose logging), and when a local script kills the boot-up, then
that can happen without the script being named.
An old Lucent winmodem script (/usr/local/etc/rc.d/ltmdm.sh) was
stopping booting of FreeBSD 5.2 after an installworld.
(The localdaemons script in /etc/rc.d/ was renamed to localpkg in
2003.)
Fix:
The file /etc/rc.d/localpkg might have code like this, added to it:
if [ `sysctl -n debug.bootverbose` -eq 1 ]; then
echo "==>" ${script}
fi
----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407030650.i636oMPI003781>