Date: Wed, 30 Jun 2004 18:15:46 GMT From: Craig Carey <research@ijs.co.nz> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/68525: Loader's verbose boot mode has rc.d/localdaemon not name local scripts Message-ID: <200406301815.i5UIFkdE065815@www.freebsd.org> Resent-Message-ID: <200406301820.i5UIKZca073610@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 68525 >Category: misc >Synopsis: Loader's verbose boot mode has rc.d/localdaemon not name local scripts >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 30 18:20:34 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Craig Carey >Release: FreeBSD 5.2-CURRENT >Organization: >Environment: i386 >Description: The Verbose boot logging of the loader is not verbose enough: nothing is displayed to the console when /etc/rc.d/localdaemon is running scripts in "/usr/local/etc/rc.d/". The ltmdm.sh script in /use/local/etc/rc.d was crashing after an upgrade from FreeBSD 5.1 to 5.2. (ltmdm.sh is of the the Lucent Winmodem FreeBSD port). Because the verbose boot mode is not verbose, echo lines would be added to scripts to diagnose the cause for the failure to boot. At least the single user boot mode ran. Also /etc/rc does not name every script when verbose mode was selected at the loader's menu. The verbose mode seemingly ought name the script that killed the boot (particularly when every option at the loader prompt won't get the FreeBSD system started). >How-To-Repeat: Select the verbose booting option at the loader prompt and have some scripts in /usr/local/etc/rc.d/ >Fix: Add an "echo -n" line to "/etc/rc.d/localdaemon", and some other lines may be added in places. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406301815.i5UIFkdE065815>