3 messages, 3 authors, 2003-08-10 · open the first message on its own page
From: Miles Lane <hidden>
Date: 2003-08-10 15:18:53
rsync -avz rsync.penguinppc.org::linux-2.4-benh . rsync: failed to connect to rsync.penguinppc.org: Connection refused rsync error: error in socket IO (code 10) at clientserver.c(83) ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2003-08-10 20:39:06
On Sun, 2003-08-10 at 17:18, Miles Lane wrote:
rsync -avz rsync.penguinppc.org::linux-2.4-benh . rsync: failed to connect to rsync.penguinppc.org: Connection refused rsync error: error in socket IO (code 10) at clientserver.c(83)
Some HW problems going on, fixed soon hopefully Ben. ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Ethan Benson <hidden>
Date: 2003-08-10 22:07:21
On Sun, Aug 10, 2003 at 08:18:53AM -0700, Miles Lane wrote:
rsync -avz rsync.penguinppc.org::linux-2.4-benh . rsync: failed to connect to rsync.penguinppc.org: Connection refused rsync error: error in socket IO (code 10) at clientserver.c(83)
its back up now. I had to move everything over to a new disk, and didn't want anyone pushing updates into thier rsync trees only to have the updates mysteriously disappaer because they occured after that part of the filesystem was dumped. reason it took so long was /dev/hda was only getting about 97K per sec transfer rates anymore. everything is back up and much much faster. -- Ethan Benson http://www.alaska.net/~erbenson/ ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/