Hi again,
So the simple way in my opinion is to use AFS.
You don't need any token or write access (except on you machine)
rsync -r --delete /afs/cern.ch/project/egee/gLite/R3.2
destination_folder
This rsync will take in the AFS R3.2 gLite repository rsync it on the
destination folder and remove the files that are no more in origin.
you just need AFS on the machine or to use the ssh connection to a
machine with AFS.
Lp
--
Louis Poncet
Where: Bat28-R-003 CERN
CH-1211 Geneve 23
Mail : [log in to unmask]
Phone: +41(0)227.674.952
On 6 oct. 09, at 14:48, Arnau Bria wrote:
> On Tue, 6 Oct 2009 14:43:21 +0200
> Louis Poncet wrote:
>
> Hi Louis,
>
>> The file that was defining the WN rpms list to define the group
>> glite- WN is now comps.xml.
>> The name of the file has not been define anywhere on our
>> documentation. We need to be able to change our settings when we
>> have to so if it is not explicit that this file name is
>> comp-glite-WN.xml in a documentation you can't rely on this file
>> name.
>> And use a proper rsync settings to do your mirror and the problem
>> will disappear on your side.
> I work more or less like Gonçalo, so I face same issues as
> him (sometimes, cause I use to upgrade once every 3/6 months).
>
> Could you please define/describe "proper rsync settings" for site
> admins like me/us? Cause if do some changes in critical files like
> comps, I don't know how to manage my local scripts.
>
> Is there any guide for creating local repo replicas?
>
>>
>> Lp
> TIA,
> Arnau
|