From: Ethan Benson <erbenson@alaska.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Rsync access through NAT?
Date: Mon, 23 Apr 2001 23:14:25 -0800 [thread overview]
Message-ID: <20010423231425.C8585@plato.local.lan> (raw)
In-Reply-To: <200104240553.HAA01467@piglet.grunz.lu>; from mlan@cpu.lu on Tue, Apr 24, 2001 at 07:53:38AM +0200
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On Tue, Apr 24, 2001 at 07:53:38AM +0200, Michel Lanners wrote:
> I have ECN compiled in all my 2.4 kernels. They are building right now
> without ECN.... We'll see.
>
> <a compile & reboot later>
there is a sysctl variable that disables this at runtime you know ;-)
i don't remember where it is offhand, sysctl -a | grep ecn or find
/proc -name '*ecn*' -print should find it.
> Yup, that seems to be the problem. rsync works again for me on
> penguinppc. So I guess that some device close to penguinppc.org doesn't
> support ECN.....
probably turning on ecn is more trouble then its worth right now,
unfortuanatly...
--
Ethan Benson
http://www.alaska.net/~erbenson/
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
next prev parent reply other threads:[~2001-04-24 7:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0104170144460.14396-100000@ash.penguinppc.org>
2001-04-17 15:31 ` Rsync access through NAT? Michel Lanners
2001-04-17 16:36 ` jeramy b smith
2001-04-24 5:53 ` Michel Lanners
2001-04-24 7:14 ` Ethan Benson [this message]
2001-04-24 7:48 ` Geert Uytterhoeven
2001-04-24 13:13 ` Michel Dänzer
2001-04-24 17:48 ` jeramy b smith
2001-04-24 19:12 ` Geert Uytterhoeven
2001-04-24 20:00 ` Michel Lanners
2001-04-24 20:51 ` Michel Dänzer
[not found] <200104250459.XAA22227@lists.linuxppc.org>
2001-04-25 21:57 ` Peter Cordes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010423231425.C8585@plato.local.lan \
--to=erbenson@alaska.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).