Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!csus.edu!ucdavis!csusac!utgard!chris
From: chris@utgard.uucp (Chris Anderson)
Newsgroups: comp.unix.questions
Subject: Re: Nasty bug in 'uucp'
Message-ID: <1991Feb7.174550.576@utgard.uucp>
Date: 7 Feb 91 17:45:50 GMT
References: <5467@bwdls58.UUCP> <226@genco.bungi.com>
Followup-To: comp.unix.questions
Distribution: na
Organization: QMA, Inc., Rancho Cordova, California
Lines: 24

In article <226@genco.bungi.com> rad@genco.bungi.com (Bob Daniel) writes:
>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 :)

Or, alias uucp to "uucp -C" and be happy.

'Course, you still need to do your backups daily :-)

Chris
-- 
+---------------------------------------------------------------+
|  Chris Anderson, QMA, Inc.  utgard!chris@csusac.ecs.csus.edu  |
|      My employer doesn't listen to me... why should you?      |
+---------------------------------------------------------------+