From: "José Luis Domingo López" <jdomingo@internautas.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Data sitting and remaining in Send-Q
Date: Mon, 24 Dec 2001 19:10:32 +0100 [thread overview]
Message-ID: <20011224181031.GA7934@localhost> (raw)
In-Reply-To: <20011224180142.E2461@lug-owl.de>
In-Reply-To: <20011224180142.E2461@lug-owl.de>
On Monday, 24 December 2001, at 18:01:42 +0100,
Jan-Benedict Glaw wrote:
> I've got some problem with a freshly installed Debian sid system.
> It's running with 2.4.16, 2.4.17-rc2 and 2.4.17 (the problem
> appears on all these kernels) and something seems to break ssh.
>
I don't know if this has something to do with your problem, but
bugs.debian.org has a _long_ list of reported bugs for ssh, many of them
with respect to ssh's X-forwarding.
My own experience with Debian's ssh is that, sooner or later,
X-forwarding fails, with Send-Q (or Recv-Q) in the server side
completely full. The server side was Debian Sid, and client side was
Debian Woody, and it happened with both a simple xclock and gkrellm (ssh
remoteserver xclock, ssh remoteserver gkrellm).
However, interactive shells didn't seem to show this problem.
--
José Luis Domingo López
Linux Registered User #189436 Debian Linux Woody (P166 64 MB RAM)
jdomingo AT internautas DOT org => Spam at your own risk
next prev parent reply other threads:[~2001-12-24 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-24 17:01 Data sitting and remaining in Send-Q Jan-Benedict Glaw
2001-12-24 18:10 ` José Luis Domingo López [this message]
2001-12-24 19:00 ` Jan-Benedict Glaw
2001-12-24 19:38 ` Jan-Benedict Glaw
2001-12-24 20:09 ` Mr. James W. Laferriere
2001-12-24 20:17 ` Jan-Benedict Glaw
2001-12-24 20:44 ` Alex Bligh - linux-kernel
2001-12-24 21:34 ` Thorsten Kranzkowski
2001-12-24 21:58 ` Jan-Benedict Glaw
2001-12-24 21:56 ` Jan-Benedict Glaw
2001-12-25 0:43 ` Alex Bligh - linux-kernel
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=20011224181031.GA7934@localhost \
--to=jdomingo@internautas.org \
--cc=linux-kernel@vger.kernel.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