Xref: utzoo comp.unix.i386:7189 comp.unix.wizards:23073
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!hsi!essnj1!smitty
From: smitty@essnj1.ESSNJAY.COM (Hibbard T. Smith JR)
Newsgroups: comp.unix.i386,comp.unix.wizards
Subject: Interactive 2.2 File zapper.
Message-ID: <772@essnj1.ESSNJAY.COM>
Date: 25 Jul 90 03:33:13 GMT
Followup-To: comp.unix.i386
Organization: ESSNJAY Systems Inc., Bethany, CT, USA
Lines: 26

Within the past 2 weeks, we've upgraded several systems from 2.0.2 to 2.2.
On one of those systems, on Sunday morning at 05:17 or thereabouts most of
the files on the system were deleted.  The problem was caused by a root
crontab driven execution of /etc/cleanup.  This system's /lost+found 
directory was inadvertently lost during the upgrade installation, and we
we're planning on recreating it on Monday morning.


The last two lines of the distributed /etc/cleanup are as follows:
--	cd /lost+found
--	find . -mtime +14 -exec rm -rf {} \;
If there's no lost and found directory in the root file system, this deletes
everything in the system that's older than 14 days. Two possible fixes exist:
-- cd /lost+found && find . -mtime +14 -exec rm -rf {} \;
-- find /lost+found -mtime +14 -exec -rm {} \;
Either of these is much safer than the distributed code.  This bad code is 
different than 2.0.2, so beware!

I hope this saves someone the grief of starting over, or worse yet, losing
a whole system when you're not prepared to rebuild it.

-- 
		Smitty
-------------------------------------------
Hibbard T. Smith JR                 smitty@essnj1.ESSNJAY.COM	
ESSNJAY Systems Inc.                uunet!hsi!essnj1!smitty