From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Virtual device in Windows 10
Date: Tue, 01 Jan 2019 21:11:00 -0000 [thread overview]
Message-ID: <17da6481-faf1-e8ca-e832-82d22f6ce9c2@SystematicSw.ab.ca> (raw)
In-Reply-To: <6e11200f-8bb6-0ad6-bb64-52b0a8757354@gmail.com>
On 2019-01-01 09:01, cyg Simple wrote:
> On 1/1/2019 2:18 AM, Gary Graham wrote:
>> I downloaded an updated version of the Cygwin tools and tried again....
>> C:\cygwin64\bin>socat -d -d pty,link=/dev/ttyV0,waitslave tcp:
>> 192.168.0.11:8023
>> 2019/01/01 01:14:27 socat[10780] N PTY is /dev/pty0
>> 2019/01/01 01:14:27 socat[10780] N opening connection to AF=2
>> 192.168.0.11:8023
>> 2019/01/01 01:14:28 socat[10780] N successfully connected from local
>> address AF=2 192.168.0.18:55426
>> 2019/01/01 01:14:28 socat[10780] N starting data transfer loop with FDs
>> [5,5] and [6,6]
>> 2019/01/01 01:14:28 socat[10780] N read(5, 0x600056500, 8192): Input/output
>> error (probably PTY closed)
>> 2019/01/01 01:14:28 socat[10780] N socket 1 (fd 5) is at EOF
>> 2019/01/01 01:14:28 socat[10780] N socket 1 (fd 5) is at EOF
>> 2019/01/01 01:14:28 socat[10780] N socket 2 (fd 6) is at EOF
>> 2019/01/01 01:14:28 socat[10780] N exiting with status 0
>> Can you tell why the PTY is closing ?
> Both ends of the processes a Cygwin process? PTY is only available to Cygwin.
What is on the other side of the virtual port?
You need either a data source/sink or an app.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
prev parent reply other threads:[~2019-01-01 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 6:38 Gary Graham
2019-01-01 7:18 ` Gary Graham
2019-01-01 16:02 ` cyg Simple
2019-01-01 21:11 ` Brian Inglis [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=17da6481-faf1-e8ca-e832-82d22f6ce9c2@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).