Hi Fabrizio,
On Fri, Jan 21, 2005 at 03:29:01PM +0000, Fabrizio Furano wrote:
> that's another story. As you remember, in December we came to an end
> with the semantics of an root:// url when used as a destination. I
> modified xrdcp to make it proceed blindly, and Andy modified the xrootd
> protocol in order to make it work without calling Stat.
>
> When the destination is not a root:// url, in my opinion the thing to
> do is to mimic the behavior in the root url case, in order to have a
> tool which behaves in the same way with both kinds of destination. But
> that behavior is a little different from the one of cp if i remember.
>
> What i'd do is to check if the two behaviors are the same, and, if
> not, to correct the one in the non-root case. And then write something
> about it in the readme.
>
> What do you think?
I'm not sure I understand. Can you give examples of how the syntax will
differ from that of 'cp'? Will it not be possible to do:
xrdcp root://host:port//x/y/z.root foobar.root
and
xrdcp root://host:port//x/y/z.root some/dir/foobar.root
(assuming "some/dir/" exists)?
Pete
> Peter Elmer wrote:
> > Hi Fabrizio,
> >
> > Ok, I'll give it a test in a bit. Did you track down the other problem?
> > (The directory one.)
> >
> > Pete
> >
> >On Fri, Jan 21, 2005 at 03:01:01PM +0000, Fabrizio Furano wrote:
> >
> >>Hi,
> >>
> >>it seems ok even under solaris. Let me know.
> >>
> >>Fabrizio
> >>
> >>Wilko Kroeger wrote:
> >>
> >>>Hello Pete
> >>>
> >>>
> >>>On Thu, 20 Jan 2005, Peter Elmer wrote:
> >>>
> >>>
> >>>
> >>>>Hi Wilko,
> >>>>
> >>>>Ok, thanks. Once I turn off the async I/O on the server the following
> >>>>works:
> >>>>
> >>>>[csfd] ~/work > xrootd/bin/xrdcp
> >>>>root://noric01.slac.stanford.edu:2525//usr/work/elmer/deepcopy16.02E.root
> >>>>.
> >>>>
> >>>>as it should. I still have the problem where:
> >>>>
> >>>>[csfd] ~/work > xrootd/bin/xrdcp
> >>>>root://noric01.slac.stanford.edu:2525//usr/work/elmer/deepcopy16.02E.root
> >>>>bogus.root
> >>>>Error Is a directory creating bogus.root
> >>>>
> >>>>creates a directory. (Clearly a separate problem.)
> >>>
> >>>
> >>>If you run a second time it will work and the file is copied to
> >>>bogus.root/bogus.root
> >>>
> >>>This behaviour is already present in previous versions. If you just
> >>>specify a name xrdcp uses it as a directory. If the target name has a '/'
> >>>it works fine, e.g.:
> >>>
> >>>xrdcp root://...////..deepcopy16.02E.root ./deepcopy16.02E.root
> >>>
> >>>I guess we should think about how the syntax should work.
> >>>
> >>>Cheers,
> >>> Wilko
> >>>
> >>>
> >>>
> >>>> Pete
> >>>>
> >>>>
> >>>>On Thu, Jan 20, 2005 at 10:59:06AM -0800, Wilko Kroeger wrote:
> >>>>
> >>>>
> >>>>>Hello Pete
> >>>>>
> >>>>>I just tried the same thing and I also see that the file is empty.
> >>>>>The xrootd by default has now the asynchronous I/O turned on. You
> >>>>>can turn it off using
> >>>>>xrootd.async off
> >>>>>in the config file (You have to create a config file and use the -c
> >>>>>option with xrootd). That should fix your problem.
> >>>>>
> >>>>>There are still problems with the current version that we see on the
> >>>>>bbrprod cluster and Andy is looking into this.
> >>>>>
> >>>>>Cheers,
> >>>>>Wilko
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>On Thu, 20 Jan 2005, Peter Elmer wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Hi Fabrizio,
> >>>>>>
> >>>>>>I just tried to use xrdcp to copy a file from one place to another and
> >>>>>>ran into a couple of problems. I'm using version xrootd
> >>>>>>20050119-0021. The
> >>>>>>client side is running RHEL3 and the server side is running SL3.
> >>>>>>
> >>>>>>On the server side I have:
> >>>>>>
> >>>>>>noric01> ls -l /usr/work/elmer/deepcopy16.02E.root
> >>>>>>-rw-r--r-- 1 elmer ec 7975402 Jan 20 10:15
> >>>>>>/usr/work/elmer/deepcopy16.02E.root
> >>>>>>
> >>>>>>and do:
> >>>>>>
> >>>>>>noric01> xrootd/bin/xrootd -p 2525 /usr/work/elmer/
> >>>>>>
> >>>>>>On the client side I tried:
> >>>>>>
> >>>>>>[csfd] ~/work > xrootd/bin/xrdcp
> >>>>>>root://noric01.slac.stanford.edu:2525//usr/work/elmer/deepcopy16.02E.root bogus.root
> >>>>>>Error Is a directory creating bogus.root
> >>>>>>
> >>>>>>The strange thing here is that it tried to create a directory:
> >>>>>>
> >>>>>>[csfd] ~/work > ls -ld bogus.root
> >>>>>>drwxr-xr-x 2 elmer bfactory 96 Jan 20 18:40 bogus.root
> >>>>>>
> >>>>>>I then tried to do:
> >>>>>>
> >>>>>>[csfd] ~/work > xrootd/bin/xrdcp
> >>>>>>root://noric01.slac.stanford.edu:2525//usr/work/elmer/deepcopy16.02E.root .
> >>>>>>[csfd] ~/work >
> >>>>>>
> >>>>>>but the result was an empty file:
> >>>>>>
> >>>>>>[csfd] ~/work > ls -ld deepcopy16.02E.root
> >>>>>>-rw-r--r-- 1 elmer bfactory 0 Jan 20 18:40
> >>>>>>deepcopy16.02E.root
> >>>>>>
> >>>>>>Any idea what is going on here?
> >>>>>>
> >>>>>> thanks,
> >>>>>> Pete
> >>>>>>
> >
> >
> >
> >
> >-------------------------------------------------------------------------
> >Peter Elmer E-mail: [log in to unmask] Phone: +41 (22) 767-4644
> >Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23, Switzerland
> >-------------------------------------------------------------------------
-------------------------------------------------------------------------
Peter Elmer E-mail: [log in to unmask] Phone: +41 (22) 767-4644
Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23, Switzerland
-------------------------------------------------------------------------
