Mirroring two systems

Thanks for reading this question, First off all, i'm quit new working with rsync. What I want is to exactly mirror a directory from one system to another system including removing non existing files on the targen if they do not exist on the source. I though that adding the parameter --delet

Re: Suspicious sizes by different C compilers

On Tue, Mar 19, 2002 at 01:29:45PM +1100, Martin Pool wrote: > On 19 Mar 2002, Zoong Pham <[EMAIL PROTECTED]> wrote: > > It is about _7 times_ smaller! > > On gcc, rsync builds by default with debug symbols included. If you > strip both executables, they should end up about the same size. You a

Re: rsync: transmitting always whole files

On 15 Mar 2002, "Schulz, Frank" <[EMAIL PROTECTED]> wrote: > Hi, > > I use rsync in the following way to update some remote files over a low > bandwidth line: >rsync -v -r -z -t -p @: > After updating from rsync 2.5.2 to 2.5.4 I noticed that modified files are > always copied completely. The

rsync 2.5.4 problem crossing file systems

Howdy, I just built this new version last week and am trying to rsync a running systems boot drive to an alternate drive on a different system (not running on the rsync drive target). The rsync seems to be crossing file system boundaries in spite of the -x flag. Can anyone help me with this pleas

Re: Suspicious sizes by different C compilers

On 19 Mar 2002, Zoong Pham <[EMAIL PROTECTED]> wrote: > Hi all, > On my Alpha box running Tru64 5.1, rsync-2.5.4 compiled by GNU gcc > 3.0.1 anh GNU make 3.79.1 has this size: 4562848. > The same version of rsync compiled by Compaq C compiler V6.3-028 and > Compaq make has this size: 655424. > It

Suspicious sizes by different C compilers

Hi all, On my Alpha box running Tru64 5.1, rsync-2.5.4 compiled by GNU gcc 3.0.1 anh GNU make 3.79.1 has this size: 4562848. The same version of rsync compiled by Compaq C compiler V6.3-028 and Compaq make has this size: 655424. It is about _7 times_ smaller! I did a quick test and they seem both

Re: (no subject)

No, --force is only relevant without --delete, as the rsync man page now says. I believe Brian's problem is that --delete doesn't make sense with --update. - Dave Dykstra On Fri, Mar 15, 2002 at 11:42:23AM -0700, [EMAIL PROTECTED] wrote: > I have a similar problem with rsync, though it's not

BSD/OS and 2.5.2-current

Hi, Ever since after 2.5.1, rsync is no longer compiling cleanly, or make testing correctly : gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c log.c -o log.o log.c: In function `log_transfer': log.c:574: warning: unused parameter `file' gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall

Re: Incremental Diffs?

> it looks like you're correct in your assesment of the problem > (i.e. the whole file is copied). You don't say what version of rsync > you're running, but there may be a bug in the current version introduced > recently with the addition of the --no-whole-file option. > See the following message

zlib problem?

Using a fresh copy of rsync 2.5.4 installed from the ports collection on FreeBSD 4.5 Release: Works fine unless I try to copy a large file with -avz, then I get: rsync: connection unexpectedly closed (1377 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151)

Re: (fwd from flepied@mandrakesoft.com) rsync dead loop

Martin Pool <[EMAIL PROTECTED]> writes: > On 16 Mar 2002, Martin Pool <[EMAIL PROTECTED]> wrote: > > > While testing a frontend to rsync, we have been bitten by rsync eating > > all the memory of the host. We have found that it was due to rsync > > trying to write an error and then failing to wr

Re: Incremental Diffs?

Kim, it looks like you're correct in your assesment of the problem (i.e. the whole file is copied). You don't say what version of rsync you're running, but there may be a bug in the current version introduced recently with the addition of the --no-whole-file option. See the following message fo

Re: rsync -f ?

I set up a case where a user has write permission on the directory, but nothing on the contents, and gotten the sync done. It complains about what it can't do, like mods to the directory, but it gets it done. Please give an example of something you can du as the user you're running rsync as

rsync -f ?

hello, I'm new with rsync (shame on me ignoring this great tool for many years!) For the following question I could not get an answer from the docs: Is it possible to run rsync in a force mode like `cp -f´ for overwriting files without write permission? I need this for a local rsync. What I'm a