Path: utzoo!attcan!uunet!spool.mu.edu!sdd.hp.com!usc!apple!vsi1!zorch!daver!kcdev!genco!rad
From: rad@genco.bungi.com (Bob Daniel)
Newsgroups: comp.unix.questions
Subject: Nasty bug in 'uucp'
Message-ID: <226@genco.bungi.com>
Date: 2 Feb 91 02:50:48 GMT
References: <5467@bwdls58.UUCP>
Reply-To: rad@genco.bungi.com (Bob Daniel)
Distribution: na
Organization: Gentry & Assoc. Excelsior Springs, MO
Lines: 17


We develop in a multi UNIX machine environment with different flavors of UNIX.
We heavily use uucp between the systems so that the program can be tested on
the other flavors of UNIX.

A few days ago, one of the  developers had a tragic experience with
uucp.  Instead of 'uucp'ing the file to another machine, he accidently used
his own machine name.  Guess what happens if you uucp a file to your own 
machine to the same directory?  It clears that file out!! Zero bytes!!  This
guy lost his entire directory (although every thing before that day was 
restred from backup).

He lost a whole day of work :(

The moral of the story... 
Treat 'uucp' like 'rm -r'.  It can do some major damage if you don't use it
correctly.  Also, do your backups daily :)