From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Problem of login (Re: GNU screen and tmux cannot read tty input if they are started in a telnet session)
Date: Sat, 16 Mar 2019 13:06:00 -0000 [thread overview]
Message-ID: <20190316220603.39fbfee580e06c3e3088d6e0@nifty.ne.jp> (raw)
In-Reply-To: <20190310150548.d5caf4e680b9d791bf4ec268@nifty.ne.jp>
Hi Corinna and Yaakov,
I know you are busy, but could you please have a look?
On Sun, 10 Mar 2019 15:05:48 +0900 Takashi Yano wrote:
> I try to clarify the title a little.
>
> On Sat, 9 Mar 2019 10:35:13 +0900 Takashi Yano wrote:
> > Hello,
> >
> > I would like to propose a patch attached for login package.
> >
> > This fixes the issue that GNU screen and tmux cannot read tty input
> > if they are started in a telnet session.
> >
> > This issue is due to the ownership of tty. With login 1.12-1, tty
> > is owned by cyg_server after logging in via telnet. This results
> > in freeze of GNU screen and tmux.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-16 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 1:35 GNU screen and tmux cannot read tty input if they are started in a telnet session Takashi Yano
2019-03-10 6:05 ` Problem of login (Re: GNU screen and tmux cannot read tty input if they are started in a telnet session) Takashi Yano
2019-03-16 13:06 ` Takashi Yano [this message]
2019-03-16 15:34 ` Corinna Vinschen
2019-03-16 16:50 ` Takashi Yano
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=20190316220603.39fbfee580e06c3e3088d6e0@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).