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 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 each path is read, sync from that src file
> > under the src dir to the corresponding dst file under the dst dir;
> > repeat until eof on stdin. That'd make it easy for a process that
> > periodically modifies one or another file in a potentially large
> > tree, to simply send notifications to a persistent rsyncer that
> > takes care of efficiently replicating those changes over to the
> > other side.
>
>
> I second that, although I haven't had the real need to have such an
> interface to rsync so far. After reading the slew of messages on this
> mailing list from people confused about --include and --exclude it's
> clear to me that it would make sense to have the option to just give
> rsync a list of files (or directories) to transfer. If I were to do
> this I would probably implement it as it's in gnu tar:
>
> rsync --files-from=FILE
>
> where FILE could be "-" to mean STDIN. This way people could do
> things such as:
>
> find /foo/bar -type f -mtime -1 -print | \
> rsync --files-from=- /foo/bar mirror:
--
Pedro Melo Cunha - <[EMAIL PROTECTED]>
Novis - Dir. Rede - ISP - Infraes. Portal <http://www.novis.pt/>
Ed. Atrium Saldanha - Pça. Dq. Saldanha, 1 - 7º / 1050-094 Lisboa
tel: +351 21 0104340 - Fax: +351 21 0104301
