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:
Or something along these lines...
-- Alberto
****************************************************************************
Alberto Accomazzi mailto:[EMAIL PROTECTED]
NASA Astrophysics Data System http://adsabs.harvard.edu
Harvard-Smithsonian Center for Astrophysics http://cfawww.harvard.edu
60 Garden Street, MS 83, Cambridge, MA 02138 USA
****************************************************************************
