Date: 29 Jun 2002 01:44:16 -0000 From: Jan Srzednicki <winfried@303.krakow.pl> To: FreeBSD-gnats-submit@FreeBSD.org Subject: conf/39976: vi recovery halting boot process Message-ID: <20020629014416.73606.qmail@spitfire.303.krakow.pl>
next in thread | raw e-mail | index | archive | help
>Number: 39976 >Category: conf >Synopsis: vi recovery halting boot process >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Jun 28 18:50:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Jan Srzednicki >Release: FreeBSD 4.6-RC i386 >Organization: Dywizjonet >Environment: System: FreeBSD spitfire.303.krakow.pl 4.6-RC FreeBSD 4.6-RC #5: Tue May 21 23:07:20 CEST 2002 root@spitfire.303.krakow.pl:/usr/obj/usr/src/sys/GRABKI i386 >Description: In some cirtumstances, the "vi recovery" thing started at boot time fails to work and the system just freezes on that point. Hitting Ctrl-C usually helps, but not always; it's quite irritating, especially when one does not use vi at all. I thing a solution would be putting some new option into rc.conf (like vi_recovery_enable="YES/NO"), which would control starting or not the vi recovery thing. >How-To-Repeat: I'm not sure why it happens; none of my servers seem to be affected, but my workstation is. >Fix: As stated above. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020629014416.73606.qmail>