1 |
Try checking the DNS resolution on the system. |
2 |
|
3 |
I had been keeping my primary system up-to-date with a nightly rsync to the gentoo servers; however, the server stopped when a DHCP Client update knocked out my /etc/resolve.conf; I had to fix it by recreating my /etc/resolve.conf as /etc/resolve.conf.head. (I probably did something stupid somewhere with env-update; I don't know how long it went so I can't say if it was my fault, emerge's fault, or env-update's fault.) |
4 |
|
5 |
Any how, once I got the DNS working again, it worked fine. Otherwise it just reported a timeout. |
6 |
|
7 |
HTH, |
8 |
|
9 |
Ben |
10 |
|
11 |
|
12 |
|
13 |
----- Original Message ---- |
14 |
From: Ross Mansfield <r.w.mansfield@×××××.com> |
15 |
To: gentoo-user@l.g.o |
16 |
Sent: Thursday, September 11, 2008 1:33:44 PM |
17 |
Subject: [gentoo-user] problem with a slow rsync server |
18 |
|
19 |
Hi, |
20 |
|
21 |
I have a rsync server on a older machine and I'm trying to emerge --sync |
22 |
another machine to the server. When I do this my emerge --sync times |
23 |
out. I'm pretty sure that it's because the rsync server is on an old |
24 |
machine (but I could be wrong) and was wondering does anyone knows how |
25 |
to increase the timeout time for emerge --sync? |
26 |
|
27 |
Thanks, |
28 |
Ross |