Well until Steve Clarified I was lost having spent all day chasing srmcp (Client tool) bug
Regards
Owem
-----Original Message-----
From: GRIDPP2: Deployment and support of SRM and local storage management on behalf of Jensen, J (Jens)
Sent: Tue 6/6/2006 2:37 PM
To: [log in to unmask]
Subject: Re: FW: FTS and Phedex
Steve Traylen wrote on 06 June 2006 14:20:
> On Tue, Jun 06, 2006 at 02:08:50PM +0100 or thereabouts, Jensen, J (Jens) wrote:
[..]
>> Now I am curious why "effectively" srmcp can't be used with
>> CASTOR? It works fine for me. Anyone knows or should I
>> ask Lassi?
>
> Looked at this last point yesterday and today. castor-srmv1 does
> of course not support SRMCP(*) so the srmcp tool can only be used
> where one of your transfer supports push or pull mode.
>
> Consequently it is impossible to use srmcp between say CERN castor
> and RAL castor.
>
> * SRMCP = SRM protocol method.
> srmcp = d-cache provide transfer client.
>
Ah, yes, of course. Thanks, Steve.
IIRC, srmCopy *is* implemented in SRM2 for CASTOR, so there's another
argument to switch. Of course that's 2.1.1 at the moment.
Personally, I prefer to call srmCopy srmCopy and to call srmcp srmcp
to distinguish the two.
-j
|