Went to copy a dir:
rsync pooped all over the place:
law> rsync -avv --progress //ishtar/root/usr/src/packages/BUILD/dictd-1.4.9 /us
r/src/packages/BUILD/
building file list ...
expand file_list to 4000 bytes, did move
199 files to consider
delta-transmission disabled for local transfer or --whole
On Thu, Dec 04, 2003 at 11:53:41PM -0800, linda w wrote:
>Went to copy a dir:
>
>rsync pooped all over the place:
>law> rsync -avv --progress //ishtar/root/usr/src/packages/BUILD/dictd-1.4.9
>/usr/src/packages/BUILD/
I doubt that rsync understands Windows '//' style paths.
--
Unsubscribe info:
If that's the case, how did rsync generate the list of files to copy?
Why would rsync
not be able to read them but cp would? Seems like an odd restriction
"rsync can read
and compare network paths, but can't actually open the paths to copy
them because
it can't understand the paths that it cre
On Fri, Dec 05, 2003 at 09:01:40AM -0800, linda w wrote:
>If that's the case, how did rsync generate the list of files to copy?
>Why would rsync not be able to read them but cp would? Seems like an
>odd restriction "rsync can read and compare network paths, but can't
>actually open the paths to co
4 matches
Mail list logo