[gentoo-amd64] emerge --sync failed

[gentoo-amd64] emerge --sync failed

[Paul Stear]

Hi all,
I'm sorry if this has been covered but I have had trouble with my mail.
I use the command eix-sync && emerge -auvtDN world && prelink -aqR to 
update my system. However, since Friday I am getting the following 
output:-
* Removing old portage-cache in /var/cache/edb/dep ...               {ok ]
 * Running emerge --sync ...
 * Problems running time emerge --sync                             [ !! ]
 * emerge --sync failed

Has anybody any ideas as to what is causing this and how to solve it?
Thanks
Paul
-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --sync failed

[Kenneth Prugh]

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

On Sat, 27 Oct 2007 14:43:03 +0100
Paul Stear <gentoo@appjaws.plus.com> wrote:

> Hi all,
> I'm sorry if this has been covered but I have had trouble with my
> mail. I use the command eix-sync && emerge -auvtDN world && prelink
> -aqR to update my system. However, since Friday I am getting the
> following output:-
> * Removing old portage-cache in /var/cache/edb/dep ...
> {ok ]
>  * Running emerge --sync ...
>  * Problems running time emerge --sync
> [ !! ]
>  * emerge --sync failed
> 
> Has anybody any ideas as to what is causing this and how to solve it?
> Thanks
> Paul

Not sure, but does `emerge --sync` actually work? That would probably
give a more detailed error than eix does.

-- 
Kenneth Prugh - Ken69267
Gentoo AMD64 Arch Tester

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] emerge --sync failed

[Paul Stear]

On Saturday 27 October 2007, Kenneth Prugh wrote:
> On Sat, 27 Oct 2007 14:43:03 +0100
>
> Paul Stear <gentoo@appjaws.plus.com> wrote:
> > Hi all,
> > I'm sorry if this has been covered but I have had trouble with my
> > mail. I use the command eix-sync && emerge -auvtDN world && prelink
> > -aqR to update my system. However, since Friday I am getting the
> > following output:-
> > * Removing old portage-cache in /var/cache/edb/dep ...
> > {ok ]
> >  * Running emerge --sync ...
> >  * Problems running time emerge --sync
> > [ !! ]
> >  * emerge --sync failed
> >
> > Has anybody any ideas as to what is causing this and how to solve it?
> > Thanks
> > Paul
>
> Not sure, but does `emerge --sync` actually work? That would probably
> give a more detailed error than eix does.

Hi, this is the error for emerge --sync:-
>>> Starting retry 2 of 3 with rsync://64.127.121.98/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) 
[receiver=2.6.9]
>>> Retrying...


>>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) 
[receiver=2.6.9]

So it appears a time out problem. What should I do now?
Thanks
Paul
-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --sync failed

[Beso]

[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]

probably the rsync has changed ip. try one of this servers:
sync = rsync://rsync.gentoo.org/gentoo-portage
#sync = rsync://rsync3.it.gentoo.org/gentoo-sources
#sync = http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/
#sync = http://mirror.ing.unibo.it/gentoo/
the first is the official one, the others should be mirrors. a full list of
rsync mirrors can be found somewhere on the gentoo site. just search for it.
the problem with your method is that you don't pass through a dns server
asking directly for an ip address and this could not work anymore when the
site you're trying has changed ip. you'd have to get again the ip. if you
want to use the ip address try searching the name with a ping or traceroute
or in some dns site like in the opendns cache site.

2007/10/27, Paul Stear <gentoo@appjaws.plus.com>:
>
> On Saturday 27 October 2007, Kenneth Prugh wrote:
> > On Sat, 27 Oct 2007 14:43:03 +0100
> >
> > Paul Stear <gentoo@appjaws.plus.com> wrote:
> > > Hi all,
> > > I'm sorry if this has been covered but I have had trouble with my
> > > mail. I use the command eix-sync && emerge -auvtDN world && prelink
> > > -aqR to update my system. However, since Friday I am getting the
> > > following output:-
> > > * Removing old portage-cache in /var/cache/edb/dep ...
> > > {ok ]
> > >  * Running emerge --sync ...
> > >  * Problems running time emerge --sync
> > > [ !! ]
> > >  * emerge --sync failed
> > >
> > > Has anybody any ideas as to what is causing this and how to solve it?
> > > Thanks
> > > Paul
> >
> > Not sure, but does `emerge --sync` actually work? That would probably
> > give a more detailed error than eix does.
>
> Hi, this is the error for emerge --sync:-
> >>> Starting retry 2 of 3 with rsync://64.127.121.98/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
> >>> Retrying...
>
>
> >>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
>
> So it appears a time out problem. What should I do now?
> Thanks
> Paul
> --
> This message has been sent using kmail with gentoo linux
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
dott. ing. beso

[-- Attachment #2: Type: text/html, Size: 3141 bytes --]

Re: [gentoo-amd64] emerge --sync failed

[Paul Stear]

On Saturday 27 October 2007, Beso wrote:
> probably the rsync has changed ip. try one of this servers:
> sync = rsync://rsync.gentoo.org/gentoo-portage
> #sync = rsync://rsync3.it.gentoo.org/gentoo-sources
> #sync = http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/
> #sync = http://mirror.ing.unibo.it/gentoo/
> the first is the official one, the others should be mirrors. a full
> list of rsync mirrors can be found somewhere on the gentoo site. just
> search for it. the problem with your method is that you don't pass
> through a dns server asking directly for an ip address and this could
> not work anymore when the site you're trying has changed ip. you'd have
> to get again the ip. if you want to use the ip address try searching
> the name with a ping or traceroute or in some dns site like in the
> opendns cache site.
>
> 2007/10/27, Paul Stear <gentoo@appjaws.plus.com>:
> > On Saturday 27 October 2007, Kenneth Prugh wrote:
> > > On Sat, 27 Oct 2007 14:43:03 +0100
> > >
> > > Paul Stear <gentoo@appjaws.plus.com> wrote:
> > > > Hi all,
> > > > I'm sorry if this has been covered but I have had trouble with my
> > > > mail. I use the command eix-sync && emerge -auvtDN world &&
> > > > prelink -aqR to update my system. However, since Friday I am
> > > > getting the following output:-
> > > > * Removing old portage-cache in /var/cache/edb/dep ...
> > > > {ok ]
> > > >  * Running emerge --sync ...
> > > >  * Problems running time emerge --sync
> > > > [ !! ]
> > > >  * emerge --sync failed
> > > >
> > > > Has anybody any ideas as to what is causing this and how to solve
> > > > it? Thanks
> > > > Paul
> > >
> > > Not sure, but does `emerge --sync` actually work? That would
> > > probably give a more detailed error than eix does.
> >
> > Hi, this is the error for emerge --sync:-
> >
> > >>> Starting retry 2 of 3 with rsync://64.127.121.98/gentoo-portage
> > >>> Checking server timestamp ...
> >
> > timed out
> > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
> > rsync.c(244) [receiver=2.6.9]
> >
> > >>> Retrying...
> > >>>
> > >>>
> > >>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage
> > >>> Checking server timestamp ...
> >
> > timed out
> > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
> > rsync.c(244) [receiver=2.6.9]
> >
> > So it appears a time out problem. What should I do now?
> > Thanks
> > Paul
> > --
> > This message has been sent using kmail with gentoo linux
> > --
> > gentoo-amd64@gentoo.org mailing list

Hi,
Thanks. I have used mirrorselect and updated make.conf and it now works.
Paul

-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Kevin Carpenter]

unsubscribe

Re: [gentoo-amd64] unsubscribe

[Volker Armin Hemmann]

On Monday 13 December 2010 13:52:03 Kevin Carpenter wrote:
> unsubscribe

nice try Kev ;)

Re: [gentoo-amd64] unsubscribe

[Dale]

Kevin Carpenter wrote:
> unsubscribe
>
>
http://www.gentoo.org/main/en/lists.xml

Dale

:-)  :-)

[gentoo-amd64] emerge --sync failed

[Paul Stear]

Hi I sent this message the other day and updated my mirror list.  Today I 
just keep getting timed out when using emerge --sync.
Any help please.

# emerge --sync
>>> Starting rsync with rsync://64.127.121.98/gentoo-portage...
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) 
[receiver=2.6.9]
>>> Retrying...


>>> Starting retry 1 of 3 with rsync://140.211.166.165/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) 
[receiver=2.6.9]
>>> Retrying...


>>> Starting retry 2 of 3 with rsync://134.68.220.74/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) 
[receiver=2.6.9]
>>> Retrying...


>>> Starting retry 3 of 3 with rsync://134.68.220.73/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) 
[receiver=2.6.9]

Thanks Paul

Hi all,
I'm sorry if this has been covered but I have had trouble with my mail.
I use the command eix-sync && emerge -auvtDN world && prelink -aqR to 
update my system. However, since Friday I am getting the following 
output:-
* Removing old portage-cache in /var/cache/edb/dep ...               {ok ]
 * Running emerge --sync ...
 * Problems running time emerge --sync                             [ !! ]
 * emerge --sync failed

Has anybody any ideas as to what is causing this and how to solve it?
Thanks
Paul
-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list


--
This email has been verified as Virus free
Virus Protection and more available at http://www.plus.net

-------------------------------------------------------

-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --sync failed

[Beso]

[-- Attachment #1: Type: text/plain, Size: 2406 bytes --]

please use names and not ip addresses!!!! remove 64.127.121.98 and add in
its place rsync.gentoo.org. the rsync server rotates so the simple ip might
not work.
remove it and use rsync.gentoo.org and use that.
and try not rsyncing more than once per 24hours or you can be temporary
banned!!!!

2007/10/29, Paul Stear <gentoo@appjaws.plus.com>:
>
> Hi I sent this message the other day and updated my mirror list.  Today I
> just keep getting timed out when using emerge --sync.
> Any help please.
>
> # emerge --sync
> >>> Starting rsync with rsync://64.127.121.98/gentoo-portage...
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
> >>> Retrying...
>
>
> >>> Starting retry 1 of 3 with rsync://140.211.166.165/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
> >>> Retrying...
>
>
> >>> Starting retry 2 of 3 with rsync://134.68.220.74/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
> >>> Retrying...
>
>
> >>> Starting retry 3 of 3 with rsync://134.68.220.73/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
>
> Thanks Paul
>
> Hi all,
> I'm sorry if this has been covered but I have had trouble with my mail.
> I use the command eix-sync && emerge -auvtDN world && prelink -aqR to
> update my system. However, since Friday I am getting the following
> output:-
> * Removing old portage-cache in /var/cache/edb/dep ...               {ok ]
> * Running emerge --sync ...
> * Problems running time emerge --sync                             [ !! ]
> * emerge --sync failed
>
> Has anybody any ideas as to what is causing this and how to solve it?
> Thanks
> Paul
> --
> This message has been sent using kmail with gentoo linux
> --
> gentoo-amd64@gentoo.org mailing list
>
>
> --
> This email has been verified as Virus free
> Virus Protection and more available at http://www.plus.net
>
> -------------------------------------------------------
>
> --
> This message has been sent using kmail with gentoo linux
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
dott. ing. beso

[-- Attachment #2: Type: text/html, Size: 3347 bytes --]

Re: [gentoo-amd64] emerge --sync failed

[Paul Stear]

On Monday 29 October 2007, Beso wrote:
> please use names and not ip addresses!!!! remove 64.127.121.98 and add
> in its place rsync.gentoo.org. the rsync server rotates so the simple
> ip might not work.
> remove it and use rsync.gentoo.org and use that.
> and try not rsyncing more than once per 24hours or you can be temporary
> banned!!!!
>
<snip>
I am not using ip addresses. (I think). I thought that rsync reads the 
mirror sites from make.conf, this is mine.
GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ 
ftp://mirror.qubenet.net/mirror/gentoo/ 
ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo 
http://pandemonium.tiscali.de/pub/gentoo/"
Would rsync itself be using ip addresses?
thanks
Paul

-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --sync failed

[Drake Donahue]

----- Original Message ----- 
From: "Paul Stear" <gentoo@appjaws.plus.com>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Monday, October 29, 2007 12:15 PM
Subject: Re: [gentoo-amd64] emerge --sync failed


> On Monday 29 October 2007, Beso wrote:
>> please use names and not ip addresses!!!! remove 64.127.121.98 and add
>> in its place rsync.gentoo.org. the rsync server rotates so the simple
>> ip might not work.
>> remove it and use rsync.gentoo.org and use that.
>> and try not rsyncing more than once per 24hours or you can be temporary
>> banned!!!!
>>
> <snip>
> I am not using ip addresses. (I think). I thought that rsync reads the
> mirror sites from make.conf, this is mine.
> GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/
> ftp://mirror.qubenet.net/mirror/gentoo/
> ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo
> http://pandemonium.tiscali.de/pub/gentoo/"
> Would rsync itself be using ip addresses?

the line ">>> Starting rsync with rsync://64.127.121.98/gentoo-portage... " 
is produced after dns resolution so yes it is.
mirror choices 1 and 4 above are currently dead when I try them,
choices 2 and 3 are responding to my browser.
Suggest you remove the GENTOO_MIRRORS=" line from /etc/make.conf
If there is a lot of turbulence in the rsync servers near you, your mirror 
select choices and/or your dns cache values may be overtaken by events and 
be invalid today although good yesterday.


> thanks
> Paul
>
> -- 
> This message has been sent using kmail with gentoo linux
> -- 
> gentoo-amd64@gentoo.org mailing list
> 

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --sync failed

[Eduardo Schoedler]

Your firewall allow traffic agains port 873 tcp/udp ?
That port is used for rsync traffic.

Best Regards,

Eduardo.


----- Original Message -----
From: "Drake Donahue" <donahue95@comcast.net>
Subject: Re: [gentoo-amd64] emerge --sync failed


----- Original Message ----- 
From: "Paul Stear" <gentoo@appjaws.plus.com>
Subject: Re: [gentoo-amd64] emerge --sync failed


> On Monday 29 October 2007, Beso wrote:
>> please use names and not ip addresses!!!! remove 64.127.121.98 and add
>> in its place rsync.gentoo.org. the rsync server rotates so the simple
>> ip might not work.
>> remove it and use rsync.gentoo.org and use that.
>> and try not rsyncing more than once per 24hours or you can be temporary
>> banned!!!!
>>
> <snip>
> I am not using ip addresses. (I think). I thought that rsync reads the
> mirror sites from make.conf, this is mine.
> GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/
> ftp://mirror.qubenet.net/mirror/gentoo/
> ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo
> http://pandemonium.tiscali.de/pub/gentoo/"
> Would rsync itself be using ip addresses?

the line ">>> Starting rsync with rsync://64.127.121.98/gentoo-portage... "
is produced after dns resolution so yes it is.
mirror choices 1 and 4 above are currently dead when I try them,
choices 2 and 3 are responding to my browser.
Suggest you remove the GENTOO_MIRRORS=" line from /etc/make.conf
If there is a lot of turbulence in the rsync servers near you, your mirror
select choices and/or your dns cache values may be overtaken by events and
be invalid today although good yesterday.


> thanks
> Paul 

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --sync failed

[Stein Burzum]

[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]

On 10/29/07, Paul Stear <gentoo@appjaws.plus.com> wrote:
>
> Hi I sent this message the other day and updated my mirror list.  Today I
> just keep getting timed out when using emerge --sync.
> Any help please.
>
> # emerge --sync
> >>> Starting rsync with rsync://64.127.121.98/gentoo-portage...
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
> >>> Retrying...
>
>
> >>> Starting retry 1 of 3 with rsync://140.211.166.165/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
> >>> Retrying...
>
>
> >>> Starting retry 2 of 3 with rsync://134.68.220.74/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
> >>> Retrying...
>
>
> >>> Starting retry 3 of 3 with rsync://134.68.220.73/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
>
> Thanks Paul
>
> Hi all,
> I'm sorry if this has been covered but I have had trouble with my mail.
> I use the command eix-sync && emerge -auvtDN world && prelink -aqR to
> update my system. However, since Friday I am getting the following
> output:-
> * Removing old portage-cache in /var/cache/edb/dep ...               {ok ]
> * Running emerge --sync ...
> * Problems running time emerge --sync                             [ !! ]
> * emerge --sync failed
>
> Has anybody any ideas as to what is causing this and how to solve it?
> Thanks
> Paul
> --
> This message has been sent using kmail with gentoo linux
> --
> gentoo-amd64@gentoo.org mailing list
>
>
> --
> This email has been verified as Virus free
> Virus Protection and more available at http://www.plus.net
>
> -------------------------------------------------------
>
> --
> This message has been sent using kmail with gentoo linux
> --
> gentoo-amd64@gentoo.org mailing list
>
>
Rsync-server needs direct connection to your computer. According to your
`timed out', are you behind firewall/NAT or something like this?

-- 
Free as in `freedom', not as beer.

[-- Attachment #2: Type: text/html, Size: 3140 bytes --]

Re: [gentoo-amd64] emerge --sync failed

[Paul Stear]

>
> Rsync-server needs direct connection to your computer. According to
> your `timed out', are you behind firewall/NAT or something like this?
Hi again,
Yes I have a router which has NAT but I do not know how to tell it to 
allow rsync.
It's strange that up until a few days ago I have had no problems 
emerge --sync or exi-sync.  Could this problem be related to some other 
cause?
I wish I was more expert in this area.
regards
Paul


-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --sync failed

[Bob Slawson]

Paul Stear wrote:
>> Rsync-server needs direct connection to your computer. According to
>> your `timed out', are you behind firewall/NAT or something like this?
> Hi again,
> Yes I have a router which has NAT but I do not know how to tell it to 
> allow rsync.
> It's strange that up until a few days ago I have had no problems 
> emerge --sync or exi-sync.  Could this problem be related to some other 
> cause?

Look at the tail end of /var/log/emerge.log and see what you have recently 
emerged.  The most painless way to do this is something like:

% genlop -l | tail -n 200 | less

Mine shows that I emerged 'sys-apps/portage-2.1.3.16' Saturday morning.  My 
guess is that you did the same, and your 'make.conf' was modified. (Did you 
'update-etc' or 'dispatch-conf' after emerging?)


Check that make.conf contains a section like this:

# Synchronizing Portage
# =====================
#
# Each of these settings affects how Gentoo synchronizes your Portage tree.
# Synchronization is handled by rsync and these settings allow some control
# over how it is done.
#
#
# SYNC is the server used by rsync to retrieve a localized rsync mirror
#     rotation. This allows you to select servers that are geographically
#     close to you, yet still distribute the load over a number of servers.
#     Please do not single out specific rsync mirrors. Doing so places undue
#     stress on particular mirrors.  Instead you may use one of the following
#     continent specific rotations:
#
#   Default:       "rsync://rsync.gentoo.org/gentoo-portage"
#   North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
#   South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
#   Europe:        "rsync://rsync.europe.gentoo.org/gentoo-portage"
#   Asia:          "rsync://rsync.asia.gentoo.org/gentoo-portage"
#   Australia:     "rsync://rsync.au.gentoo.org/gentoo-portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
#
# PORTAGE_RSYNC_RETRIES sets the number of times portage will attempt to retrieve
#     a current portage tree before it exits with an error. This allows
#     for a more successful retrieval without user intervention most times.
#PORTAGE_RSYNC_RETRIES="3"
#
# PORTAGE_RSYNC_EXTRA_OPTS can be used to feed additional options to the rsync
#     command used by `emerge --sync`. This will not change the default options
#     which are set by PORTAGE_RSYNC_OPTS (don't change those unless you know
#     exactly what you're doing).
#PORTAGE_RSYNC_EXTRA_OPTS=""
#

The 'SYNC' variable is the important one:

> I wish I was more expert in this area.
> regards
> Paul
> 

BobS

-- 
gentoo-amd64@gentoo.org mailing list