On Wed, Dec 17, 2003 at 01:27:42PM +0900, Charles Nadeau wrote:
> Max Kipness wrote:
>
> >> Another option is to upgrade to the CVS version (available in
> >> the near future as version 2.6.0) and use the --files-from
> >> option to specify your files (since it already parses the
> >> names one pe
Max Kipness wrote:
>> Another option is to upgrade to the CVS version (available in
>> the near future as version 2.6.0) and use the --files-from
>> option to specify your files (since it already parses the
>> names one per line).
>
> Charles,
>
> Based on what was just said above, I am using Ba
Wayne Davison wrote:
> On Tue, Dec 16, 2003 at 08:08:53PM -0600, Max Kipness wrote:
>> Based on what was just said above, I am using Bash version 2.05b.0(1),
>> and no extra configs for splitting are necessary as it splits
>> appropriately at the end of the line.
>
> No, bash splits on all whites
Wayne Davison wrote:
> On Tue, Dec 16, 2003 at 08:08:53PM -0600, Max Kipness wrote:
>> Based on what was just said above, I am using Bash version 2.05b.0(1),
>> and no extra configs for splitting are necessary as it splits
>> appropriately at the end of the line.
>
> No, bash splits on all whites
Max Kipness wrote:
>> Anything I could do besides trying to escape the space or
>> putting the whole directory between double quote?
>
> Not sure what the problem is. Could it be an OS issue? I noticed a
Max,
I am using Gentoo 1.4.
Thanks!
Charles
> difference in general with the way Redhat
On Tue, Dec 16, 2003 at 09:00:06PM -0600, Max Kipness wrote:
> You are right about the splitting above, however I can use spaces in
> my include file without issue.
Yes, the include/exclude files are entirely parsed by rsync, so there
are no shell-compatibility issues there. The problem Charles i
> > Based on what was just said above, I am using Bash version
> 2.05b.0(1),
> > and no extra configs for splitting are necessary as it splits
> > appropriately at the end of the line.
>
> No, bash splits on all whitespace by default. Take a file like this:
>
> one two three
> four
On Tue, Dec 16, 2003 at 08:08:53PM -0600, Max Kipness wrote:
> Based on what was just said above, I am using Bash version 2.05b.0(1),
> and no extra configs for splitting are necessary as it splits
> appropriately at the end of the line.
No, bash splits on all whitespace by default. Take a file l
> On Wed, Dec 17, 2003 at 09:05:50AM +0900, Charles Nadeau wrote:
> > backup=`cat /etc/snapshot/include.text` rsync -va [...] $backup
> > $backuproot/$type.1/
>
> This is entirely a shell issue -- the shell you are using is
> splitting the args at all whitespace, and you need to tell it
> to st
>
> >> > I am trying to rsync folders/files hosted on a Windows
> machine to a
> >> > Linux machine. Many of the directory names have spaces in them.
> >> > How can I list them in a file so that the --include-from
> option use
> >> > them correctly?
> >> > Thanks!
> >> >
> >> > Charles
> >>
10 matches
Mail list logo
