From: Andries Brouwer <aebr@win.tue.nl>
To: Andrew Barton <andrevv@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: forkpty with streams
Date: Fri, 25 Jul 2003 17:27:51 +0200 [thread overview]
Message-ID: <20030725152751.GA606@win.tue.nl> (raw)
In-Reply-To: <1059089316.8596.14.camel@localhost>
On Thu, Jul 24, 2003 at 11:28:36PM +0000, Andrew Barton wrote:
> I've got the 2.4 kernel, and I'm trying to use the forkpty() system call
forkpty is not a system call
> with the standard I/O stream functions. The calls to forkpty() and
> fdopen() and fprintf() all return successfully, but the data never seems
> to get to the child process.
> pid = forkpty (&fd, 0, 0, 0);
> if (pid == 0) {
> execlp ("sh", "sh", (void *)0);
> } else {
> F = fdopen (fd, "w");
> fprintf (F, "exit\n");
> fflush (F);
> wait (0);
> }
Let me see. Your sh gets input from this pseudotty and sends its
output there again. But you never read that filedescriptor.
No doubt things will improve if you let the parent read from fd.
Andries
next prev parent reply other threads:[~2003-07-25 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 23:28 forkpty with streams Andrew Barton
2003-07-25 13:02 ` Doug McNaught
2003-07-25 15:27 ` Andries Brouwer [this message]
2003-07-25 10:59 ` Andrew Barton
2003-07-25 18:46 ` Matti Aarnio
2003-07-25 12:53 ` Andrew Barton
2003-07-25 20:10 ` Andries Brouwer
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=20030725152751.GA606@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=andrevv@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 NNTP newsgroup(s).