From: Stephen Carrier <carrier@berkeley.edu>
To: Peter Board <p_board@hotmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Cygwin 3.1.5, 3.1.6 and 3.1.7 builds reporting tty errors with OpenSSH Services in indows Event Logs
Date: Tue, 15 Sep 2020 09:22:30 -0700 [thread overview]
Message-ID: <20200915162230.GA14401@iguana.crashland.org> (raw)
In-Reply-To: <PSXP216MB0326EB9E66CDF66CED3EAA609A230@PSXP216MB0326.KORP216.PROD.OUTLOOK.COM>
On Mon, Sep 14, 2020 at 08:18:53AM +0000, Peter Board via Cygwin wrote:
> Hi,
>
> I am trying to update our Cygwin libraries at work, which we use on many servers to provide OpenSSH services.
> I have been making update packages for many years from a Cygwin install on a development server, and went to update our systems to the latest OpenSSH 8.3p1 build.
>
> However after making the update package, I found that the Windows Event Log (or if Syslogd is setup – which we do have in our general Cygwin deployment /var/log/messages) gets two errors when using any version of the Cygwin Libraries after the 3.1.4 build.
>
>
> Sep 14 12:06:48 hostname sshd: PID 2093: error: Failed to disconnect from controlling tty.
>
> Sep 14 12:06:48 hostname sshd: PID 2093: error: ioctl(TIOCSCTTY): Operation not permitted
Can this be reproduced in a standard cygwin install? It seems as if
your have a customized environment where you compile your own packages,
and updated the cygwin libs perhaps w/o updating openssh at the same time.
Stephen
next prev parent reply other threads:[~2020-09-15 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 8:18 Peter Board
2020-09-15 16:22 ` Stephen Carrier [this message]
2020-09-15 23:46 ` Peter Board
2020-09-17 16:16 ` Stephen Carrier
2020-09-17 16:51 ` Takashi Yano
[not found] ` <PSXP216MB03268C87FE0C80D06B7A79E99A3E0@PSXP216MB0326.KORP216.PROD.OUTLOOK.COM>
2020-09-18 0:10 ` Takashi Yano
2020-09-18 1:44 ` Peter Board
2020-09-19 1:18 ` Takashi Yano
2020-09-23 5:45 ` Peter Board
2020-09-24 11:21 ` Takashi Yano
2020-09-24 23:51 ` Peter Board
2020-09-27 4:25 ` Andrey Repin
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=20200915162230.GA14401@iguana.crashland.org \
--to=carrier@berkeley.edu \
--cc=cygwin@cygwin.com \
--cc=p_board@hotmail.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).