From: Joel Salomon <chesky@plan9.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] waitpid
Date: Tue, 7 Nov 2006 20:25:53 -0500 [thread overview]
Message-ID: <a3d7246e57090d7e8829e4b984ae7cd5@plan9.jp> (raw)
In-Reply-To: <fa8e1e860a0715b7fdc8c832d7193dd3@plan9.jp>
> Don't bother submitting a patch; I've updated the SOURCE section of wait(2).
That was half my patch.
> You didn't need the source to get the answer to your question
> either; note the phrase `These routines set errstr.' and see
> intro(2) for what this means.
Is waiting without children considered an error condition? Checking…
waitpid returned -1: no living children
…looks like. OK, a lack of understanding on my part; never mind.
--Joel
next prev parent reply other threads:[~2006-11-08 1:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 1:02 Joel Salomon
2006-11-08 1:08 ` Joel Salomon
2006-11-08 1:13 ` geoff
2006-11-08 1:10 ` Russ Cox
2006-11-08 1:15 ` Joel Salomon
2006-11-08 1:25 ` Joel Salomon [this message]
2006-11-08 1:28 ` Bruce Ellis
2006-11-08 2:30 ` Federico Benavento
2006-11-08 6:55 ` Bruce Ellis
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=a3d7246e57090d7e8829e4b984ae7cd5@plan9.jp \
--to=chesky@plan9.jp \
--cc=9fans@cse.psu.edu \
/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).