From: Steve Graegert <graegerts@gmail.com>
To: Karol Banczyk <car-los@tlen.pl>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: ophan child process to take standard input
Date: Mon, 5 Sep 2005 07:33:35 +0200 [thread overview]
Message-ID: <6a00c8d505090422337beed9a0@mail.gmail.com> (raw)
In-Reply-To: <dfffk2$fp8$1@sea.gmane.org>
On 9/4/05, Karol Banczyk <car-los@tlen.pl> wrote:
> Hello,
> I'm solving an exercise from my school. Not to go into details - the
> task is to create a initiating process which in turn starts three new
> processes and then finishes its work. The three processes are to
> communicate with pipes. There's no problem till this stage. But there's
> the catch. The first of the three processes has to get its input from
> the standard input and this works only as long as the parent
> (initiating) process is alive. When the parent finishes the standard
> input goes back to bash and the orphaned processes are adopted by the
> init process having no access to stdin.
This is what I would expect. As long as the parent is running child
processes are attached to the process group's controlling terminal and
will be detached automatically when the parent is terminated.
Normally, the parent should wait (waitpid) for its childs to prevent
them of becoming orphans. Are you waiting for them?
It would be easier to help if you would let us know what the exercise is.
Regards
\Steve
--
Steve Graegert <graegerts@gmail.com>
Software Consultancy {C/C++ && Java && .NET}
Mobile: +49 (176) 21248869
Office: +49 (9131) 7126409
next prev parent reply other threads:[~2005-09-05 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 18:49 ophan child process to take standard input Karol Banczyk
2005-09-05 5:33 ` Steve Graegert [this message]
2005-09-05 17:42 ` Karol Banczyk
2005-09-05 18:01 ` 386 demand paged pure executable Nanakos Chrysostomos
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=6a00c8d505090422337beed9a0@mail.gmail.com \
--to=graegerts@gmail.com \
--cc=car-los@tlen.pl \
--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).