Date: Mon, 3 Jun 2002 16:29:58 -0700 (PDT) From: twig les <twigles@yahoo.com> To: Fernando Gleiser <fgleiser@cactus.fi.uba.ar> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 4.4 Release vi problem Message-ID: <20020603232958.62452.qmail@web10104.mail.yahoo.com> In-Reply-To: <20020603201233.Y78390-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Damn, you nailed it again. I did a 'cp -R /var/tmp/vi.recover /var/tmp/vi.recover.backup'. Then a rm -rf /var/tmp/vi.recover. At boot it mentioned that it couldn't find /var/tmp/vi.recover (but still booted fine) so I threw a 'touch /var/tmp/vi.recover' for good measure and it works like new again. Thanks again. BTW, I didn't need to use the /var/tmp/vi.recover.backup, the system works fine (to my knowledge...). --- Fernando Gleiser <fgleiser@cactus.fi.uba.ar> wrote: > On Mon, 3 Jun 2002, twig les wrote: > > > Well you nailed it. My DNS server was still set > to my > > old one. Once I changed that it let me in right > away > > via ssh. And netstat -a works fine too (again). > > Thnx. > > > > The vi problem still happens. I tried vi -r after > it > > booted and it recovered snort.conf, but on reboot > it > > hangs again. This is really weird cause Snort > still > > works fine.... > > If you don't care about those recover files, you can > just > 'rm /var/tmp/vi.recover/'. > > No files to recover, no hang trying to recover them > =0) > > > Fer > ===== ----------------------------------------------------------- Only failures don't include failing in their plans ----------------------------------------------------------- __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020603232958.62452.qmail>