This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: TIOCSTI or workaround?
- From: Greywolf <greywolf at starwolf dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 25 Jun 2017 21:04:17 -0700
- Subject: Re: TIOCSTI or workaround?
- Authentication-results: sourceware.org; auth=none
- References: <16ace46e-4409-03b5-04b4-32974ae2aed3@starwolf.com>
On 2017-06-25 20:58, Greywolf wrote:
Greetings,
I have a program I've writ which takes input and types on to other
terminals; however, it seems that under Cygwin, TIOCSTI on a file
descriptor doesn't work according to plan -- I get "Invalid argument",
but I don't know why.
Did a read on ioctl, and saw something about POSIX STREAMS. I thought
that paradigm had died a mean nasty ugly death YEARS back, but I'm
hoping that's entirely beside the point.
Does there exist a way to successfully call
ioctl(fd, TIOCSTI, (char *)cp)
or is there a workaround?
Addendum:
I used the "standard" TIOCSTI definition of:
#define TIOCSTI 0x5214
[or whatever it is, under Linux -- can't check right now]. Perhaps it
is just that IOCTL directive which is out of whack. Basic conceptual
question still stands...
--
--*greywolf;
--
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