On Thu, Jul 28, 2005 at 05:35:30PM +0100 or thereabouts, Dr D J Colling wrote:
> Thanks all,
> So this works if I replace sfn with srm. Now, given this is part of a cms
> MC production script and that we have a mixture of srm and and classic SEs
> out there, is there any automatic way to tell which is which? In practise
> this is not a real problem as we specify which SE that it goes to, however
> I would still be interested to know if there any automated method or if we
> are just hope that all the non srm SEs just go away.
You have the choice of specifying an SE hostname or a SURL and nothing in between.
An SE hostname
In reality if you are going to specify an exact SURL then you must have
a pretty good idea about what the SARoot is (e.g. /pnfs/gridpp.rl.ac.uk/data/cms) is so
finding out or recording the se type is going to be an equivalent amount of work.
CMS, as I understand it, don't have logical file names above a SURL?
> All the best,
> d "numpty" c
> On Thu, 28 Jul 2005, Graeme A Stewart wrote:
> > Sansum, RA (Andrew) wrote:
> > > In case someone else was baffled by the use of the word numpty I include the following:
> > >
> > > http://www.urbandictionary.com/define.php?term=numpty
> > we werna in a fankle up here, aye.
> > Steve Traylen wrote:
> > >>
> > >>lcg-cr --vo cms file:/home/cmsprod/ttt -d
> > >>sfn://gfe02.hep.ph.ic.ac.uk:8443/pnfs/hep.ph.ic.ac.uk/data/cms/ttt
> > >
> > >
> > > Try
> > >
> > > lcg-cr --vo cms file:/home/cmsprod/ttt -d
> > > srm://gfe02.hep.ph.ic.ac.uk:8443/pnfs/hep.ph.ic.ac.uk/data/cms/ttt
> > sfn:// was the storage URL for a classic SE. srm:// is the SURL for an
> > SRM enabled SE (dCache, DPM, etc.).
> > GFAL probably just translates sfn:// into gsiftp:// for a transport URL
> > (given that it finds out the SE is of type "disk"), but for an srm://
> > the TURL can be quite different (and indeed, even on a different host).
> > However, the SRM protocol takes care of that part of the negotiation...
> > graeme
[log in to unmask]