From: Andrey Repin <anrdaemon@yandex.ru>
To: Peter Board <p_board@hotmail.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: Sun, 27 Sep 2020 07:25:55 +0300 [thread overview]
Message-ID: <19310153666.20200927072555@yandex.ru> (raw)
In-Reply-To: <PSXP216MB032612EFB205F9B04FA129C99A390@PSXP216MB0326.KORP216.PROD.OUTLOOK.COM>
Greetings, Peter Board!
Please no top posting in this channel.
>> On Wed, 23 Sep 2020 05:45:19 +0000
>> Peter Board wrote:
>>> I’ve sanitised the output, replacing DOMAIN and my user name in this output
>>>
>>> F:\cygwin64\bin>ls -l /dev/*ty*
>>> crw-rw-rw- 1 my_admin_user Domain Users 5, 0 Sep 23 15:44 /dev/tty
>>>
>>> I also generated the ls output when connected via ssh, as otherwise the /dev/pty0 doesn’t exist
>>>
>>> $ ls -l /dev/*ty*
>>> crw------- 1 my_admin_user Domain Users 136, 0 Sep 23 15:39 /dev/pty0
>>> crw-rw-rw- 1 my_admin_user Domain Users 5, 0 Sep 23 15:39 /dev/tty
>>>
>>> icacls F:\cygwin64\dev
>>> F:\cygwin64\dev NULL SID:(DENY)(Rc,S,REA,WEA,X,DC)
>>> DOMAIN \my_admin_user:(F)
>>> DOMAIN\Domain Users:(RX,W,DC)
>>> NT AUTHORITY\SYSTEM:(RX,W,DC)
>>> BUILTIN\Administrators:(RX,W,DC)
>>> Everyone:(RX)
>>> CREATOR OWNER:(OI)(CI)(IO)(F)
>>> CREATOR GROUP:(OI)(CI)(IO)(RX)
>>> Everyone:(OI)(CI)(IO)(RX)
>>>
>>> Successfully processed 1 files; Failed processing 0 files
>
>> The results seem to be normal...
> Yesterday I tried adjusting the CYGWIN= values to do with symlink creation,
> but that didn’t seem to , tried lnk, native, restrictnative but the errors persisted.
First, it's nativestrict, f.e.
CYGWIN=wincmdln winsymlinks:nativestrict glob:ignorecase
second, changing env. var alone won't help. ou have to recreate links
themselves.
--
With best regards,
Andrey Repin
Sunday, September 27, 2020 7:23:49
Sorry for my terrible english...
prev parent reply other threads:[~2020-09-27 4:35 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
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 [this message]
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=19310153666.20200927072555@yandex.ru \
--to=anrdaemon@yandex.ru \
--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).