Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!think!husc6!spdcc!gnosys!gst
From: gst@gnosys.UUCP (Gary S. Trujillo)
Newsgroups: comp.sys.att
Subject: Re: 3b1 startup: I CAN'T BELIEVE at&t was really this stupid!
Keywords: destructive cleanup
Message-ID: <245@gnosys.UUCP>
Date: 10 Jul 89 03:13:51 GMT
References: <1989Jul5.151150.25280@eci386.uucp> <1640@sialis.mn.org> <293@ecijmm.UUCP> <1655@sialis.mn.org>
Reply-To: gst@gnosys.UUCP (Gary S. Trujillo)
Organization: gst's 3B1 - Somerville, Massachusetts
Lines: 17

I may be missing something, but it seems to me that if the command under
discussion:

   #find /lost+found -mtime +7 -type d -exec rm -rf {} \; >/dev/null 2>&1

had any real utility, it would be to clean *files* out of the /lost+found
directory.  As the command is written, it will actually delete the /lost+found
directory itself along with its contents if the contents of the directory have
not been modified within the past week.  If there is no /lost+found directory
when you run fsck as part of the reboot sequence, there is no place to put
files which have become unlinked.

Just an observation.

-- 
Gary S. Trujillo			      {linus,bbn,m2c}!spdcc!gnosys!gst
Somerville, Massachusetts		     {icus,ima,stech,wjh12}!gnosys!gst