From: Tim Moore <timoore@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Stan Cox <scox@redhat.com>, Frysk List <frysk@sourceware.org>
Subject: Re: fhpd <program>
Date: Wed, 07 Mar 2007 13:43:00 -0000 [thread overview]
Message-ID: <45EEC184.8010700@redhat.com> (raw)
In-Reply-To: <45ED9747.9000003@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrew Cagney wrote:
> Hi Stan,
>
> I'm not sure what you mean by never regains I/O control.
>
> One key issue though is wiring the child process up to a
> frysk.sys.PseudoTerminal - otherwise the process and fhpd will be
> fighting over control of the terminal. Don't forget that there are two
> cases to handle:
I checked in changes that implement the "run" command in the CLI command
line. It will be quite easy to adapt the fhpd program to pass an
argument to run a program named in its arguments. This works well for
our simple looping test cases, but I also didn't think about the
terminal issue.
>
> - fhpd command line where it clearly should create the PTY
What should the other side of the pty be bound to? An xterm?
> - UI where the pty will be part of a Terminal panel and the code should
> bind the created process to that
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFF7sGEeDhWHdXrDRURAkSCAKCmIQytNY8hY7bbvWLOBQ65iEgarACfc/3x
HfdWe0wEDL53GNbmNkNQrT0=
=PsgH
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-03-07 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 16:15 Stan Cox
2007-03-06 16:31 ` Andrew Cagney
2007-03-07 13:43 ` Tim Moore [this message]
2007-03-07 21:51 ` Andrew Cagney
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=45EEC184.8010700@redhat.com \
--to=timoore@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=scox@redhat.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).