> -----Original Message-----
> From: GRIDPP2: Deployment and support of SRM and local storage management
> [mailto:[log in to unmask]] On Behalf Of Greig A Cowan
> Sent: 24 August 2005 16:10
> To: [log in to unmask]
> Subject: Re: Another item for workshop
>
> Hold on a minute, I think there is some confusion here (well, at least I
> am confused).
>
> When ssh keys were first mentioned on this thread, it was referring to
> having *password-less* login to dCache's ssh admin interface. Derek has
> stated that this uses rsa1 keys.
>
> Mona: Does IC have this facility setup?
I was referring to our setup in which we can run script using
admin-interface on the head-node. It requires password just once.
[root@gfe02 root]# ssh dcacheadm < aug24
Pseudo-terminal will not be allocated because stdin is not a terminal.
admin@gfe02's password:
dCache Admin (VI) (user=admin)
(local) admin > cd sedsk00_1
(sedsk00_1) admin > rep rm 00010000000000000000FB70 -force
.............
............
> Edinburgh and IC both have pool nodes running non-SL3 operating systems.
> In these cases, instead of running the full LCG middleware stack on the
> pool nodes (including security etc) we only have the dCache software
> installed. If you also want a gridftp door on the pool node, it is
> necessary to have the dcache.kpwd file (essentially the grid-map-file). In
> order to do this, a quick fix/hack is to set up a cron job to copy over
> the dcache.kpwd file from the admin node. In order to do this, ssh-keys
> are required. This procedure is detailed here:
>
> http://wiki.gridpp.ac.uk/wiki/DCache_FAQ#Non-SL3.2FNon-LCG_Pool_node
This is completely different issue!
> Let me know if this still isn't making sense.
>
> Cheers,
> Greig
>
>
====================================
Mona Aggarwal
Tel. (+44) 20 759 47809
Imperial College London
High Energy Physics Department
Prince Consort Road, London, SW7 2BW
====================================
|