> " " == Otto Wyss <[EMAIL PROTECTED]> writes:
> I want to mirror any i386 packages from a debian package mirror
> with the following command
> rsync -avvP --include-from="file"
> ftp.at.debian.org::debian-ftp/debian-non-US/pool/non-US/main
> /mirror/debian/non-US/ma
we are using rsync version 2.4.6 to perform backups to our backup
servers. All machines are running Solaris 2.6 and are located on the
same network. From time to time rsync fails, and we get an error exit
with a status 20. Does anybody know what that means and how we can
avoid this problem?
T
> " " == Lenny Foner <[EMAIL PROTECTED]> writes:
> Date: Thu, 4 Jan 2001 10:22:38 -0600 From: Dave Dykstra
> <[EMAIL PROTECTED]>
> I like that idea. I would call it "--only-from".
> One corner case to consider is: What happens when one of the
> pathnames in
I want to mirror any i386 packages from a debian package mirror with the
following command
rsync -avvP --include-from="file"
ftp.at.debian.org::debian-ftp/debian-non-US/pool/non-US/main /mirror/debian/non-US/main
while "file" contains
+"_all"
+"_i386"
-"*"
+"*/"
But the -"*" does not work, all
I also see hangs on large datasets. Very frustrating as I can't seem to find
any messages in the logs that would indicate where the problam may lie. Also
only on pulls, not on pushes.
August
On Thu, Jan 04, 2001 at 12:12:43PM +1000, [EMAIL PROTECTED] wrote:
> Dave_Dykstra_ wrote:
> > Because of the piplined nature of the rsync implementation and the
> > back-and-forth nature of the rsync protocol, rsync stresses many TCP
> > implementations. No one else has mentioned a problem with F
>One corner case to consider is: What happens when one of the
>pathnames in the list turns out to be a directory?
First we should sync the permissions on the directory, per opts. Same
for character/block specials. Plain files are not the only nodes in the
filesystem.
Are you sure we want to
Dave,
Sure, I'll go ahead and benchmark the difference. I should be able to get
something out by this weekend. I do think this optimization should be made,
I can think of a bunch of situations where the design of the system means
the programmer has extra information that could improve efficiency
> " " == Dave Dykstra <[EMAIL PROTECTED]> writes:
> In versions 2.3.2 and earlier, rsync had an optimization that I
> put in such that if the end of the list was --exclude '*' and
> the earlier includes didn't have any wildcards, it would skip
> the recursive traversal of t
Date: Thu, 4 Jan 2001 10:22:38 -0600
From: Dave Dykstra <[EMAIL PROTECTED]>
I like that idea. I would call it "--only-from".
One corner case to consider is: What happens when one of the
pathnames in the list turns out to be a directory? My advice it to
keep it absolutely as simple
On Wed, Jan 03, 2001 at 05:25:42PM -0500, Alberto Accomazzi wrote:
> In message <[EMAIL PROTECTED]>, Bennett Todd writes:
>
> > Even nicer, in my opinion, would be a mode where rsync could be told
> > to take a src dir and a dst dir as cmdline args, then simply reads
> > paths from stdin, and as
Hi!
I think this would be the most important modification in rsync to
improve our performance... We rsync 1 gb with more than 300k files each
10 minutes, to several clients, and it's extremelly heavy on the I/O
and CPU...
On Wed, Jan 03, 2001 at 05:25:42PM -0500, Alberto Accomazzi wrote:
> In me
These questions look like they might not be a job for rsync. Anybody ever try
(cd sourcedir;cat filelist |cpio -ocdum |rsh remotehost "cd destdir;cpio -vicdum")
? It won't have any of the enhancements or rsync, but these examples look like they
don't need them. Heck, you can even set that c
On Wed, Jan 03, 2001 at 05:03:41PM -0500, Bennett Todd wrote:
> Even nicer, in my opinion, would be a mode where rsync could be told
> to take a src dir and a dst dir as cmdline args, then simply reads
> paths from stdin, and as each path is read, sync from that src file
> under the src dir to the
14 matches
Mail list logo
