similar to: preserving symlinks

Hi, sorry if this is old stuff, but I did my best to look first... Have been getting errors along these lines: mv mydir mdir.2002 ln -s mydir.2002 mydir Then update mirror with rsync -av --delete-after. Without --delete-after, no problem, with --delete-after, get a code 23. The attached shell script will recreate the error (on my machine, at any rate). Just run it from a clean directory.

Hello. Recently, I started using rsync to backup files in my root partition on an Ensim box over to a remote machine. The remote machine 'pulls' from the Ensim box using the following: rsync -arvzx --exclude=/proc --exclude=/tmp --exclude=/mnt --delete --delete-excluded -e ssh 192.168.0.1:/ /bkup/rootpart/ The problem is, if I 'df' the Ensim box, it reports that the entire

There is a new patch named "delete-during.diff" in the CVS "patches" dir. This patch adds the ability for rsync to incrementally delete files in each directory during the normal course of the transfer rather than doing a separate delete scan either before or after the transfer. The patch renames the current --delete option into --delete-before and makes --delete behave in the

I've been using the --keep-dirlinks feature of 2.6.3pre1. I also use -x (--one-file-system) and --delete-after. The symlinked directories on the receiver are symlinked to a partition other than the one where the target of the rsync resides (that's the whole point of this nifty --keep-dirlinks feature). I discovered that the symlinked directories are not being processed for deletions.

our daily backup is done using the rdiff-backup tool, which in turn utilizes rsync/librsync to do the actual mirroring work. a few days ago we did a refactoring and renamed a bunch of directories. for backward compatibility we maintain the old names by symlinking it to the new names. so, for example, oldname1/ now becomes newname1/, and oldname1 is now a symlink to newname1/. we found that

I am a Newbie Nitwit. Here's the problem session: rsync -tvv rsync.dsbl.org::dsbl/rbldns-fresh-list.dsbl.org opening tcp connection to rsync.dsbl.org port 873 rsync: The server is configured to refuse --recursive (-r) rsync error: requested action not supported (code 4) at clientserver.c(473) rsync: connection unexpectedly closed (4 bytes

I'm using 2.6.3pre1 to transfer a rather large Debian archive (126GB, more than 30 million files). It contains about 450 daily snapshots, where unchanged files are hardlinked between the snapshots (so many files have hunderds of links). It's been running for some time now, and I found that while it's far from done, it's already used 165GB on the receiving end. Investigation shows

Hello, I bumped in to issue with rsync 2.5.6 while doing "sync" of large files. Here is the error message.... "write failed on cm3.0_hpux11.11_final.tar : Error 0 rsync error: error in file IO (code 11) at receiver.c(243) rsync: connection unexpectedly closed (13342 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165)" There is lot

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey there, when i try to sync two directories or files containing a "-" character in ther path, rsync fails: # /usr/bin/rsync --partial -rcvaLe "ssh -o UserKnownHostsFile=/dev/null -o \ StrictHostKeyChecking=no" --progress "user@server:/path/band - album/" "/path/" this gives an error like: rsync: on remote

This is a patch made by the redhat folks. I noticed it in their src.rpm for rsync while I was updating it for 2.5.7. I figure at the worst, it's a nice bit of protection. It would be cool to get this put into CVS. -- Kees Cook kees@kernel.org -------------- next part -------------- --- rsync-2.4.6/main.c.foo Fri Aug 17 11:46:03 2001 +++ rsync-2.4.6/main.c Fri Aug 17 11:45:37 2001 @@

Hello! I need to do rsync between local drives on win32. Rsync works, but it never ends. I started it with -vv and it writes something like: total: matches=0 tag_hits=0 false_alarms=0 data=0 And then it stays forever. :-( Could you help me?

Hi all Here is the egrep result : egrep "SIZEOF|LONGLONG" build_mipsel/rsync-2.6.3/config.h /* #undef HAVE_LONGLONG */ #define SIZEOF_INT 4 #define SIZEOF_LONG 4 #define SIZEOF_SHORT 2 and the HAVE_LONGLONG config.log result : rsync_cv_HAVE_LONGLONG=cross Is there a problem with this values ? Thanks a lot for your answer Best regards, Florian

When using rsync -avv to recursively copy a local directory on a remote server, and if the remote server has a symbolic link of the same name pointing to some other directory, then that remote symlink is clobbered in favor of the hard-wired path. I looked at the man page and other rsync documentation about copying links, but not of the options seemed to apply in my case. The closest was

Nota: Se adjunt? el mensaje reenviado. _________________________________________________________ Do You Yahoo!? Informaci?n de Estados Unidos y Am?rica Latina, en Yahoo! Noticias. Vis?tanos en http://noticias.espanol.yahoo.com -------------- next part -------------- An embedded message was scrubbed... From: michael mendoza <mike114x@yahoo.com> Subject: Re: rsync + ssh -o -p -g -l Date:

Hi, I want to mirror NetBSD on this server: ftp://ftp.univ-orleans.fr/logiciel-libre/netbsd-ftp/ The problem is I dont want to mirror old versions (1.5.x) There are 1.5* branches as subdirs of 'packages' and others at the root of the server called 'NetBSD-release-1-5' and 'NetBSD-1.5.3'. I want to avoid to sync them. The command I use to sync is: - - - - - - - - - - -

Hi, I am having one machine which i want to configure as a rsync server. Onthe machine I had kept the following file /etc/rsyncd.conf motd file = /etc/rsyncd.motd log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [rsync-test] path = /home/xidcit/test comment = XIDC Rsync Server uid = nobody gid = nobody read

So I'm doing daily backups with rsync, and weekly, I run it with --delete after archiving the whole thing (this way I don't lose any deleted files). All week long this runs fine, but when I add --delete, rsync runs for a few hours then aborts because the box runs out of memory. Jan 30 06:31:09 backup kernel: Out of Memory: Killed process 3490 (rsync). Source box: RH8+Custom Patches Rsync

On Tue, Sep 16, 2003 at 03:49:45AM -0700, jw schultz wrote: > > Aside from numerous other weaknesses that have crept into > the manpage i do note that there doesn't seem to be any > point where it is mentioned that rsync replaces destination > files rather than updating them in-place. I'm not sure > where it would go in the current manpage. > > I'm no writer

Hello Everyone, Would it be posiable to add a "keep alive" option to rsync. The problem I am having is that the connection is dropped while rsync is scanning the local directory. If "null" packets are send to the server every 60 seconds or so, the connection will stay up and the sync will work. Or maybe there is an option that does this already ? Thanks, Pieter De Wit

Hello. I'm having a problem using rsync to copy my root partition to a new disk. This disk has a previous copy on it, and rsync seems determined to (unnecessarily) delete files from it. Worse, despite the fact that the files DO exist on the source, it does not update the destination, leaving me with less than I had before?! Here's my usage: ] server# /usr/local/bin/rsync -naxv --delete