Date: Mon, 1 Jul 2002 04:30:06 -0700 (PDT) From: Peter Pentchev <roam@ringlet.net> To: freebsd-bugs@FreeBSD.org Subject: Re: conf/39976: vi recovery halting boot process Message-ID: <200207011130.g61BU6J8097689@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/39976; it has been noted by GNATS. From: Peter Pentchev <roam@ringlet.net> To: Jan Srzednicki <winfried@303.krakow.pl> Cc: bug-followup@FreeBSD.org Subject: Re: conf/39976: vi recovery halting boot process Date: Mon, 1 Jul 2002 14:27:57 +0300 On Sat, Jun 29, 2002 at 01:44:16AM -0000, Jan Srzednicki wrote: > > >Number: 39976 > >Category: conf > >Synopsis: vi recovery halting boot process > >Arrival-Date: Fri Jun 28 18:50:02 PDT 2002 > >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. The 'vi recovery' code in the startup scripts searches for files in the /var/tmp/vi.recovery/ directory named recover.*; if any such files are found, it attempts to e-mail the user whose editing session crashed. The fact that the recovery code is attempting to do something would seem to imply that the startup scripts have found such recover.* files, which would mean that maybe somebody *was* actually using vi(1) or something else that generated that kind of files :) Thus, the most probable reason for the 'vi recovery' taking a long time would be some misconfiguration of that machine's mail server/client. The startup scripts attempt to send mail using the 'sendmail' command, so a properly set up /etc/mail/mailer.conf file in addition to a mail server or a null-mailer running on that machine, should work fine. > 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. If you are really, really sure that no one would be using vi, and that no notification of crashed sessions is necessary, you could add a simple shell script in /usr/local/etc/rc.d/, named, say, remove-recover.sh, which would execute a 'rm -rf /var/tmp/vi.recovery/recover.*' command :) > >How-To-Repeat: > > I'm not sure why it happens; none of my servers seem to be affected, > but my workstation is. > > >Fix: Configure your workstation's mail server, maybe to a simple mail relay (null-mailer)? G'luck, Peter -- Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence claims to be an Epimenides paradox, but it is lying. 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?200207011130.g61BU6J8097689>