The backend rcopy resource doesn't create a directory for the source files to
reside in.
For example, say I have a directory ssh://foo@a/dir/ containing three files:
1.txt, 2.txt and 3.txt. If I attempt to rcopy that directory to
gridftp://foo@b/, then I'll end up with those text files in gridftp://foo@b/
and not in a new gridftp://foo@b/dir/ directory as I would have expected.
Dropping the trailing slash from the source directory doesn't work either, as
there's an assert in FileRCopyResource.http_POST.RCopyCommand specifically
checking for this.
Original issue reported on code.google.com by ahunter.ccg@gmail.com on 7 Jul 2011 at 7:41
Original issue reported on code.google.com by
ahunter.ccg@gmail.com
on 7 Jul 2011 at 7:41