rad@genco.bungi.com (Bob Daniel) (02/02/91)
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 :)
chris@utgard.uucp (Chris Anderson) (02/08/91)
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? | +---------------------------------------------------------------+