Check out your /tmp directory.  You should find a directory called something
like "vi.recover". Take a look at the files in there. If you don't need any
of them,
delete them and your machine will not hang there for so long (btw, you can
CTRL-C when it's "recovering vi editor sessions" to skip that). I would assume
that using vi's recover feature would also alleviate the problem, but I've
never
used it. This situation happens when a terminal is closed in which vi is
editing
a file (or if you kill a vi process that has a file open).

-Tim


At 09:55 PM 4/2/01 , you wrote:
>Ok, this actually happens on my FreeBSD system, but maybe I'l just throw it
>out here for fun-
>(Don't wanna resub to the FreeBSD lists)
>
>But my "slow vi" problem is only on bootup, when it's "recovering vi editor
>sessions"-
>This box is a 486-50, and works perfectly as a router/nat box, but goddamn-
>Sometimes when it boots, it sits at "recovering vi editor sessions" for
>about 5 minutes.
>Other times, it takes 10 seconds (regardless of any vi usage as far as I
>could tell)
>I have done the usual homework and can not find out exactly what is
>happening in this part of the bootup sequence-
>Any ideas?
>Or is this a FreeBSD-specific issue?
>--
>

--
Timothy A. Musson
NASA's John Glenn Research Center at Lewis Field
Software Engineer (Zin Technologies)
SAMS-II Project               It's not the size of the dog in the fight,
216-977-0608                  It's the size of the fight in the dog.
mussont@zin-tech.com