I do not think there would be a problem using ssh as the shell. The cat
trick or using - is basically the same thing as specifying the file
names manually.
On Wed, 2003-01-08 at 03:42, Lorenzo Bettini wrote:
> jw schultz wrote:
> > On Tue, Jan 07, 2003 at 07:15:27PM +0100, Lorenzo Bettini wrote:
On Wed, Jan 08, 2003 at 09:42:39AM +0100, Lorenzo Bettini wrote:
> jw schultz wrote:
> >On Tue, Jan 07, 2003 at 07:15:27PM +0100, Lorenzo Bettini wrote:
> >
> >>Aaron Morris wrote:
> >>
> >>>You did not specifically mention it: compression (-z) would probably
> >>>help more than anything. Otherw
jw schultz wrote:
On Tue, Jan 07, 2003 at 07:15:27PM +0100, Lorenzo Bettini wrote:
Aaron Morris wrote:
You did not specifically mention it: compression (-z) would probably
help more than anything. Otherwise, you could do something like:
Have a file (ie filelist.txt) that contains the filen
We've been calling this option --files-from rather than --file-list,
to be like the GNU tar option.
On Sun, Jan 05, 2003 at 09:55:50AM -0800, Wayne Davison wrote:
> On Sat, Jan 04, 2003 at 05:03:02PM -0800, jw schultz wrote:
> > that would produce destloc/srcdir/
> > when you might want a copy
On Tue, Jan 07, 2003 at 07:15:27PM +0100, Lorenzo Bettini wrote:
> Aaron Morris wrote:
> >You did not specifically mention it: compression (-z) would probably
> >help more than anything. Otherwise, you could do something like:
> >
> >Have a file (ie filelist.txt) that contains the filename (with
Aaron Morris wrote:
You did not specifically mention it: compression (-z) would probably
help more than anything. Otherwise, you could do something like:
Have a file (ie filelist.txt) that contains the filename (with relative
paths), one file per line.
rsync -rRWz `cat filelist.txt` user@hos
On Sun, Jan 05, 2003 at 12:44:32PM -0800, Wayne Davison wrote:
> On Sun, Jan 05, 2003 at 11:55:22AM -0800, jw schultz wrote:
> > The first problem is this would flatten things unless you used
> > relative and forced the user's CWD. That would cause considerable
> > confusion.
>
> Really? This is
On Sun, Jan 05, 2003 at 11:55:22AM -0800, jw schultz wrote:
> The first problem is this would flatten things unless you used
> relative and forced the user's CWD. That would cause considerable
> confusion.
Really? This is exactly how rsync works now with multiple file names on
the command-line,
On Sun, Jan 05, 2003 at 09:55:50AM -0800, Wayne Davison wrote:
> On Sat, Jan 04, 2003 at 05:03:02PM -0800, jw schultz wrote:
> > that would produce destloc/srcdir/
> > when you might want a copy of srcdir at destloc instead of
> > in destloc.
>
> Ah yes, I _was_ missing something. However, I
On Sat, Jan 04, 2003 at 05:03:02PM -0800, jw schultz wrote:
> that would produce destloc/srcdir/
> when you might want a copy of srcdir at destloc instead of
> in destloc.
Ah yes, I _was_ missing something. However, I still don't think we need
to clutter rsync with two types of --file-list op
On Sat, Jan 04, 2003 at 04:02:23PM -0800, Wayne Davison wrote:
> On Sat, Jan 04, 2003 at 12:40:05PM -0800, jw schultz wrote:
> > One specifying subpaths and the other for those having a shared
> > prefix.
>
> I don't see why this is needed. For instance, your example of a shared
> prefix:
>
> >
On Sat, Jan 04, 2003 at 12:40:05PM -0800, jw schultz wrote:
> One specifying subpaths and the other for those having a shared
> prefix.
I don't see why this is needed. For instance, your example of a shared
prefix:
> find srcdir | myfilter | rsync --file-list - srcdir destloc
would be eas
Please bear in mind that I am quickly approacing areas where I have
little expertise.
Commenting on the recursion issue:
I thought rsync already takes intermediate directories into account. If
you specify -p, does not rsync create the intermediate directories with
the same perms as the source
On Sat, Jan 04, 2003 at 08:00:20PM +0100, wim delvaux wrote:
> On Saturday 04 January 2003 19:49, Aaron Morris wrote:
> > It has already been suggested in this list, as well as by myself in the
> > rsync wishlist for a new option to specify a file that has a list of
> > files to be transferred.
>
I usually use rsync 2.5.4 on AIX and compression is not enabled by
default. 2.5.5 may be different.
Another important option would be to use "-u" since it would only
transfer a file if it has changed (even if it is in the file list).
wim delvaux wrote:
On Saturday 04 January 2003 19:49, Aaron
On Saturday 04 January 2003 19:49, Aaron Morris wrote:
> You did not specifically mention it: compression (-z) would probably
> help more than anything. Otherwise, you could do something like:
I thought it was on by default ?
>
> Have a file (ie filelist.txt) that contains the filename
You did not specifically mention it: compression (-z) would probably
help more than anything. Otherwise, you could do something like:
Have a file (ie filelist.txt) that contains the filename (with relative
paths), one file per line.
rsync -rRWz `cat filelist.txt` user@hostname::module
The on
HI all,
efficiency question for VERY low bandwith networks
Suppose I know the list of files that are changed
What is the most efficient way to make rsync sync this list.
Currently I use --include-from --exclude to generate a 'filelist' but I
suspect that client and/or server exchange the list o
18 matches
Mail list logo
