Uhm... rsync developers: what do you think about changing the default
modify-window in the Cygwin platform?
It seems to me that many problems people have are just because of the
granularity of timestamp.
Maybe changing the default could be the best choice. That would be
documented in the man
Title: Message
Hello
-
Can someone please
clarify the meaning of these stats. This is the rsync'ing of one file remotely
over a wan.
Total file size:
383219712 bytesTotal transferred file size: 383219712 bytesLiteral data:
3143680 bytesMatched data: 380076032 bytes
The total file size
Yes, I know that's a newbie question.
I want to rsync a tree SERVER1:/src/repository to
SERVER2:/otherlocation/repository
with one rsync command.
Under repository are the directories
foo and
foo/bar/foo
Now I want to rsync foo/bar/foo but not foo.
I want to use the --exclude-from switch (to
--- jw schultz [EMAIL PROTECTED] wrote:
On Wed, Jan 08, 2003 at 02:15:13PM -0800, Dan Kressin wrote:
I'm currently syncing the home directories on two boxes with the syntax:
dest-host# rsync -av -e ssh --delete --progress source-host:/home/
/home/
That's working well. Now I want to
On Thu, Jan 09, 2003 at 01:02:29PM +0100, Lapo Luchini wrote:
Uhm... rsync developers: what do you think about changing the default
modify-window in the Cygwin platform?
It seems to me that many problems people have are just because of the
granularity of timestamp.
Maybe changing the
Dave Dykstra wrote:
it would fail if it were
talking to a release of rsync that is too old to recognize the option[...]. The surprise factor on that may be too much to make it worthwhile.
I agree. I didn't think about that.
But, given the resilience to upgrade many people have, you sure are
On Thu, Jan 09, 2003 at 07:48:50AM -0600, Max Kipness II wrote:
Total file size: 383219712 bytes
Total transferred file size: 383219712 bytes
Literal data: 3143680 bytes
Matched data: 380076032 bytes
The total file size is definitely correct, but what I don't understand
is the transfered
I'm trying to use rsync to make a local copy of only
a subset of a directory tree: all directories, and all
files within CVS/ directories, but nothing else.
I thought this might work:
rsync -av --include '*/' --include 'CVS/*' --exclude '*' src src_cvs
It does recursively copy all
On Thu, Jan 09, 2003 at 05:52:43PM +0100, Lapo Luchini wrote:
Dave Dykstra wrote:
it would fail if it were
talking to a release of rsync that is too old to recognize the
option[...]. The surprise factor on that may be too much to make it
worthwhile.
I agree. I didn't think about
On Thu, Jan 09, 2003 at 11:32:30AM -0600, Dave Dykstra wrote:
The only way to do it would be to modify the protocol to include the info
instead of passing a parameter.
I realize this may sound like heresy, but would it not be worthwhile in terms
of code simplification/robustness to break
-- wrote:
Yes, I know that's a newbie question.
I want to rsync a tree SERVER1:/src/repository to
SERVER2:/otherlocation/repository
with one rsync command.
Under repository are the directories
foo and
foo/bar/foo
Now I want to rsync foo/bar/foo but not foo.
I want to use the
I am preparing for making 2.5.6pre1 today and decided to submit David
Staples patch with a little rework. Here's the version I submitted.
- Dave Dykstra
--- main.c~ Thu Aug 1 15:46:59 2002
+++ main.c Thu Jan 9 12:43:55 2003
@@ -26,6 +26,16 @@
extern struct stats stats;
extern int
On Thu, Jan 09, 2003 at 12:30:30PM -0500, David Eisner wrote:
I thought this might work:
rsync -av --include '*/' --include 'CVS/*' --exclude '*' src src_cvs
If things were working correctly, yes, that would indeed work. The
problem is that the 'CVS/*' item has an interior slash, and rsync
On Thu, Jan 09, 2003 at 10:36:33AM -0600, Dave Dykstra wrote:
On Thu, Jan 09, 2003 at 01:02:29PM +0100, Lapo Luchini wrote:
Uhm... rsync developers: what do you think about changing the default
modify-window in the Cygwin platform?
It seems to me that many problems people have are just
To Mike and the Rsync community,
This is by far
the greatest utility I have ever used for backing up an entire system.
My Redhat server got botched during an upgrade. I reformatted my partitions
and installed a minimal system. Rsync'ed the entire / directory back and
the server came back to
On Thu, Jan 09, 2003 at 01:20:08AM -0400, Carlos Molina wrote:
Hi.
I'm trying to accomplish the following ;
1) First, I did a rsync for a file, like this
/usr/bin/rsync -lptgoD --delete --rsh=/usr/bin/ssh -R --delete-excluded
-vv [EMAIL PROTECTED]:/usr/local/src/* /tmp/localhost/daily.0
I went ahead and submitted Hideaki's patch pretty much as is. I took off
the ifdef around the memset at the beginning of client_sockaddr() because
I figured it wouldn't hurt to do anywhere. Besides, it was checking
for a specific operating system (__linux__) which we like to avoid and
because
On Thu, Jan 09, 2003 at 11:21:36PM +0100, Lapo Luchini wrote:
jw schultz wrote:
The 2 second timestamp resolution only applies to some
windows filesystems. I think NTFS has timestamp resolution
in the milliseconds (unlrelated to precision). It should
only become an issue when the windows
jw schultz wrote:
This message says it is 2 seconds aso on NTFSD actually:
http://lists.samba.org/pipermail/rsync/2000-July/002491.html
I don't use windows myself. I just recall that one of the
windows filesystem has timestamps in the milliseconds.
I also thought that, but that mesage
I'm working on trying to get rsync 2.5.6pre1 available for people to
test more widely. I'm out of time for today, and I'm stuck on a problem
that some machines on build.samba.org are showing on the 'chgrp' test.
I can reproduce this on my home redhat 7.3 system too. It appears to be a
timing
On Thu, Jan 09, 2003 at 05:09:07PM -0600, Dave Dykstra wrote:
I'm working on trying to get rsync 2.5.6pre1 available for people to
test more widely. I'm out of time for today, and I'm stuck on a problem
that some machines on build.samba.org are showing on the 'chgrp' test.
I can reproduce
I just did a make clean to tidy up a bit and found four
objects were missed. The seem to belong to the CHECK_PROGS
set. Not sure where best to put them so created a
CHECK_OBJS variable and added it to the clean rule.
--
On Thu, Jan 09, 2003 at 05:09:07PM -0600, Dave Dykstra wrote:
It's very hard to debug because it is a timing problem and because it
happens after rprintf handling is already shut down in the child process.
Fortunately fprintf(stderr, ...) always works, even in the child process.
This is what
jw schultz wrote:
The 2 second timestamp resolution only applies to some
windows filesystems. I think NTFS has timestamp resolution
in the milliseconds (unlrelated to precision). It should
only become an issue when the windows filesystem is the
destination.
This message says it is 2 seconds
Date: Thu Jan 9 21:14:10 2003
Author: dwd
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv5654
Modified Files:
NEWS access.c acconfig.h clientname.c config.h.in configure
configure.in rsyncd.conf.5 rsyncd.conf.yo
Log Message:
Support IPv6 addresses with
25 matches
Mail list logo
