From: Suriya Narayanan M S <mssnlayam@cs.annauniv.edu>
To: linux-c-programming@vger.kernel.org
Subject: opening standard streams - who does that?
Date: Sat, 6 Jul 2002 21:00:55 +0530 [thread overview]
Message-ID: <200207070223.g672NSH26418@cs.annauniv.edu> (raw)
Hi all,
I want to know who opens the streams
stdin, stdout, stderr in file-descriptors 1, 2, 3
and calls the process. I know (right or wrong?)
that on a fork the filedescriptors are duplicated.
So bash or the shell can just forks a new process
without assinging the fds. Is it the kernel
which assigns 0 to the keyboard. How is this
done?
Thanks in advance,
Suriya Narayanan M S
--
Guru Brahma Gurur Vishnu
Gurur Dhevo Maheshwaraha
Gurur Saakshaath Parabramha
Thasmai Shree Gurave Namaha
Public key at www.keyserver.net
next reply other threads:[~2002-07-06 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-06 15:30 Suriya Narayanan M S [this message]
2002-07-07 7:26 ` opening standard streams - who does that? Glynn Clements
2002-07-08 17:53 ` Chuck Winters
2002-07-08 20:27 ` Marius Nita
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=200207070223.g672NSH26418@cs.annauniv.edu \
--to=mssnlayam@cs.annauniv.edu \
--cc=linux-c-programming@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).