Hi Karl,
> With "voms-proxy-info -all" I get the output below. Let me know
> if/when I should try "uberftp rb01.pic.es pwd".
>
> Thanks, Karl.
>
> subject : /C=UK/O=eScience/OU=Cambridge/L=UCS/CN=karl
> harrison/CN=proxy/CN=proxy
> issuer : /C=UK/O=eScience/OU=Cambridge/L=UCS/CN=karl harrison/CN=proxy
> identity : /C=UK/O=eScience/OU=Cambridge/L=UCS/CN=karl harrison/CN=proxy
> type : proxy
> strength : 1024 bits
> path : /usera/harrison/.globus/proxy
> timeleft : 114:00:52
> === VO lhcb extension information ===
> VO : lhcb
> subject : /C=UK/O=eScience/OU=Cambridge/L=UCS/CN=karl harrison
> issuer : /DC=ch/DC=cern/OU=computers/CN=voms.cern.ch
> attribute : /lhcb/Role=user/Capability=NULL
> attribute : /lhcb/Role=NULL/Capability=NULL
> attribute : nickname = karl (lhcb)
> timeleft : 114:00:52
> uri : voms.cern.ch:15003
That looks OK. You can try uberftp against various endpoints:
uberftp rb01.pic.es pwd
uberftp wms203.cern.ch pwd
uberftp wms216.cern.ch pwd
|