From: william@hq.newdream.net (Will Yardley)
To: zsh-users@sunsite.auc.dk
Subject: Re: Unusual message: client_input_channel_req
Date: Thu, 15 Aug 2002 16:03:30 -0700 [thread overview]
Message-ID: <20020815230330.GA5535@hq.newdream.net> (raw)
In-Reply-To: <15708.11690.510679.396626@paullew-ultra.cisco.com>
Paul Lew wrote:
> I am still on zsh 4.0.5 (solaris 2.6). When I exit out of a remote
> ssh session, I saw this displayed:
>
> clefairy paullew ~> exit
> client_input_channel_req: channel 0: wrong channel: -1
> channel_lookup: -1: bad id
> client_input_channel_req: channel -1: unknown channel
> cns-build2 paullew destiny>
>
> Any idea what these are and should I be concerned about them? Thanks.
This looks like a problem with ssh and not with zsh.
--
Will Yardley
input: william < @ hq . newdream . net . >
next prev parent reply other threads:[~2002-08-15 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 22:39 Paul Lew
2002-08-15 23:03 ` Will Yardley [this message]
2002-08-15 23:16 ` Paul Lew
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=20020815230330.GA5535@hq.newdream.net \
--to=william@hq.newdream.net \
--cc=zsh-users@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).