Re: [eclipse-mirrors] Size of a full Eclipse mirror?

[Carlos Carvalho <carlos@xxxxxxxxxxxxxx>]

archive-admin@xxxxxxxxxxxxxxxxx (archive-admin@xxxxxxxxxxxxxxxxx) wrote on 9 July 2010 11:22:
 >On Thu, 8 Jul 2010, Carlos Carvalho wrote:
 >
 >> archive-admin@xxxxxxxxxxxxxxxxx (archive-admin@xxxxxxxxxxxxxxxxx) wrote on 8 July 2010 17:33:
 >> >Ok our deletetions are trailing due to io errors, I have enabled
 >> >--delete-during which should help matters and tweeked my chmod line so we
 >> >dont det io erros having mirrored a closed directory.
 >> >  --chmod=Du+rwx,u+rw   Providing your mirroring is done by a
 >> >different user than the webserver is running will probably
 >> >prevent alot of io errors on your side if mirroring direct from eclipse.
 >>
 >> The chmod won't help because the IO errors happen due to wrong
 >> permissions at the origin, not the destination.
 >>
 >Not strictly true for instance rsync will create a dir it cant traverse 
 >local or files it can not delete eg a dir with say 600 perms and then fall 
 >over on the local listing from then on etc...
 >
 >rsync://download.eclipse.org/eclipseMirror/tools/ajdt/36/update/
 >Has a number of dirs without user exec perms for example

Sure. The chmod is standard procedure and all mirrors should always
use it. Eclipse is not the only repository with inapropriate
permissions for the owner...

I mean that it won't solve the eclipse problem because it's caused by
the scanning at the origin, not at the destination.

An easy way for the eclipse admins to cludge around the issue is to
run the rsync daemon as root for this module (making sure use chroot
is enabled). Another way is the mirrors going on strike until they fix
it :-)