Xref: utzoo comp.sys.att:6514 comp.unix.questions:13777
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!njin!princeton!jonlab!jon
From: jon@jonlab.UUCP (Jon H. LaBadie)
Newsgroups: comp.sys.att,comp.unix.questions
Subject: Re: Reattach inode to lost&found / what file is it?
Summary: ksh history files end up there too.
Keywords: fsck lost&found inode
Message-ID: <782@jonlab.UUCP>
Date: 21 May 89 13:56:52 GMT
References: <1099@adds.newyork.NCR.COM> <2060@umbc3.UMBC.EDU>
Followup-To: comp.unix.questions
Organization: 4455 Province Line Rd., Princeton, NJ 08540
Lines: 14

In article <2060@umbc3.UMBC.EDU>, alex@wolf.umbc.edu (Alex Crain) writes:
> 
> .... Most
> of the files that I find in lost+found are intermediate files from the 
> compiler, representing changes in the inode table that never got flushed to 
> disk.

As the summary says, if the system goes down, even on an orderly shutdown,
you may find the working copy of your ksh's history file unconnected and
moved to the lost+found.
-- 
Jon LaBadie
{att, princeton, bcr}!jonlab!jon
{att, attmail, bcr}!auxnj!jon