From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: RE: PATCH: Re: zpty and controlling tty (and other fd's)
Date: Thu, 4 May 2000 15:33:17 +0200 (MET DST) [thread overview]
Message-ID: <200005041333.PAA02841@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Thu, 4 May 2000 14:55:13 +0400
Andrej Borsenkow wrote:
> > On True64 Unix O_NOCTTY is implicit and cannot be unset. How weird.
>
> Hmm ... if I correctly recall, first tty opened by process becomes
> controlling tty. It means, that if child has closed all of it's file
> descriptors and reopens tty for stdin (duplicating it for stdout,
> stderr) - it gets it as controlling tty. It should be fairly portable.
What I said with the above is that on True64 Unix opening a terminal
in a process with no controlling tty does *not* make that terminal the
controlling tty of the process.
So: `how weird'.
> ...
>
> 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.
> And 13 is left over from wordcode file mapping. Mapping itself
> goes away after exec (at least here - I expect, it should be true for
> all Unices) - but we have to close fd anyway.
Ah, right. I don't use wordcode files in development versions.
This adds the closedumps() function and makes it be called in zpty.c
and zexecve(). Does anyone know of other places where it should be
called?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-05-04 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 13:33 Sven Wischnowsky [this message]
2000-05-04 13:48 ` nslookup (function) problem Andrej Borsenkow
2000-05-05 16:57 ` PATCH: Re: zpty and controlling tty (and other fd's) Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
2000-05-04 13:34 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=200005041333.PAA02841@beta.informatik.hu-berlin.de \
--to=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).