[Cooker] Re: the rsync madness gotta stop!!!

2001-12-13 Thread Brian J. Murrell

On Thu, Dec 13, 2001 at 09:18:40AM -0600, Dan Mack wrote:
 
 It happened to me too.  Luckily I caught it before all was lost with a
 ctrl-c.

There is a real simple way to prevent the damage --delete and a bad
mirrir can do.  In the directory where your ccoker tree is, *before*
doing an rsync, simply make a shadow copy using hard links:

$ cd /path_to_cooker
$ cp -la cooker cooker.bak
$ rsync --madness

This creates a complete mirror of your tree before rsync can destroy
it.  But it does so without taking up any additional space (before
rsyncing).  Once you are successfully rsynced, remove the shadow with
rm -r.  If rsync destroys your cooker tree, you can restore it
easily and try again later.

b.


-- 
Brian J. Murrell




Re: [Cooker] Re: the rsync madness gotta stop!!!

2001-12-13 Thread Dan Mack

On Thu, 2001-12-13 at 12:43, Brian J. Murrell wrote:
 On Thu, Dec 13, 2001 at 09:18:40AM -0600, Dan Mack wrote:
  
  It happened to me too.  Luckily I caught it before all was lost with a
  ctrl-c.
 
 There is a real simple way to prevent the damage --delete and a bad
 mirrir can do.  In the directory where your ccoker tree is, *before*
 doing an rsync, simply make a shadow copy using hard links:
 
 $ cd /path_to_cooker
 $ cp -la cooker cooker.bak
 $ rsync --madness
 
 This creates a complete mirror of your tree before rsync can destroy
 it.  But it does so without taking up any additional space (before
 rsyncing).  Once you are successfully rsynced, remove the shadow with
 rm -r.  If rsync destroys your cooker tree, you can restore it
 easily and try again later.

Ack, that works.   I've just set the --max-delete arg on rsync something
comfortably small so I only lose a little bit from now on.

Dan
-- 
Dan
--
Dan Mack [EMAIL PROTECTED]
http://www.macktronics.com