Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tekcrl!tekgvs!sail!terryl
From: terryl@sail.LABS.TEK.COM
Newsgroups: comp.unix.wizards
Subject: Re: Is System V.4 fork reliable?
Message-ID: <7900@tekgvs.LABS.TEK.COM>
Date: 31 Jul 90 17:09:35 GMT
References: <480@amanue.UUCP> <13426@cbmvax.commodore.com> <573@oglvee.UUCP> <13435@smoke.BRL.MIL>
Sender: news@tekgvs.LABS.TEK.COM
Reply-To: terryl@sail.LABS.TEK.COM
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 10

In article <573@oglvee.UUCP> jr@oglvee.UUCP (Jim Rosenberg) writes:
-But if system calls fail simply because of a very temporary bout of activity,
-that is *not my problem*!  It's the kernel's problem.  At least it should be:
-that's what "I'm paying the kernel for" so to speak.  And *I CAN'T FIX IT*
-myself.  If utilities haven't been rewritten to do the right thing with EAGAIN
-after fork(), and I'm only a binary licensee, what can I do about it?


     Bitch and moan to your OS vendor; after all, to use some of your own
logic, "That's what I'm paying the kernel for", so to speak....