From: Billy O'Connor <billy@oconnoronline.net>
To: elapus@ntsp.nec.co.jp
Cc: linux-c-programming@vger.kernel.org
Subject: Re: error in system call
Date: Fri, 14 Jun 2002 00:59:21 -0400 (EDT) [thread overview]
Message-ID: <20020614045921.85CA689@dps7.oconnoronline.net> (raw)
In-Reply-To: <LFEIJFMKHCJIHBFOGINPGELPCBAA.elapus@ntsp.nec.co.jp>
while ( (pid = fork()) < 0 );
would result to an infinite loop if
such limit is reached.
>>I COULD BE WRONG WITH THIS<<
No, I believe you're correct. I'd at least do:
while ( (pid = fork()) < 0 )
sleep(n);
--
Billy O'Connor
next prev parent reply other threads:[~2002-06-14 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 20:51 error in system call Earl R. Lapus
2002-06-14 4:59 ` Billy O'Connor [this message]
2002-06-14 11:13 ` Glynn Clements
2002-06-14 12:14 ` Mohammed Khalid Ansari
2002-06-14 13:33 ` Glynn Clements
-- strict thread matches above, loose matches on Subject: below --
2002-06-14 5:07 Singh, Umesh K (MED)
2002-06-14 5:06 Mohammed Khalid Ansari
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=20020614045921.85CA689@dps7.oconnoronline.net \
--to=billy@oconnoronline.net \
--cc=elapus@ntsp.nec.co.jp \
--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).