From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: Re: zpty and controlling tty (and other fd's)
Date: Fri, 5 May 2000 20:57:34 +0400 [thread overview]
Message-ID: <002601bfb6b3$025c5530$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200005041333.PAA02841@beta.informatik.hu-berlin.de>
> >
> > Note fd's 3 and 13. 3 is master side of pty (child does not need it,
> > does it?)
>
> Of course I tried to close it -- and on Linux this messed up the
> parent's (i.e. the shell's) terminal settings. Don't know how this
> came.
>
Well, at least Midnight and Screen do it - so, it is possible. This one
is from Midnight code that spawns subshell. I do not know, how usefulr
it is.
/* {{{ Open the slave side of the pty: again */
pty_slave = pty_open_slave (pty_name);
/* This must be done before closing the master side of the pty,
*/
/* or it will fail on certain idiotic systems, such as Solaris.
*/
/* Close master side of pty. This is important; apart from
*/
/* freeing up the descriptor for use in the subshell, it also
*/
/* means that when MC exits, the subshell will get a SIGHUP and
*/
/* exit too, because there will be no more descriptors pointing
*/
/* at the master side of the pty and so it will disappear.
*/
close (subshell_pty);
I do not use Linux, but until this is cleared there - porbably under
#ifndef __LINUX (or whatever)?
-andrej
next prev parent reply other threads:[~2000-05-05 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 13:33 Sven Wischnowsky
2000-05-04 13:48 ` nslookup (function) problem Andrej Borsenkow
2000-05-05 16:57 ` Andrej Borsenkow [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-04 13:34 PATCH: Re: zpty and controlling tty (and other fd's) Sven Wischnowsky
2000-05-04 9:44 Sven Wischnowsky
2000-05-04 10:55 ` Andrej Borsenkow
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='002601bfb6b3$025c5530$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).