Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: Who is responsible for a retry
Message-ID: <13486@smoke.BRL.MIL>
Date: 5 Aug 90 02:30:46 GMT
References: <866@mwtech.UUCP> <1809@necisa.ho.necisa.oz> <35@kings.co.uk>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 14

In article <35@kings.co.uk> lls@kings.UUCP (Superuser) writes:
>The shell springs to mind! What are you suggesting? I make the trivial
>addition of rewriting the shell??

If you had been following the discussion, you should have already heard
that the shell DOES retry failed forks, several times with exponentially
increasing delay between them.

>People are missing the whole point here.  The vast majority of Un*x
>users are binary only licencees and cannot easily change their code to
>deal with EAGAIN returns in all of their (binary only) programs.

If you have a problem with a program you've licensed in binary form,
you should submit a bug report to the vendor of the program.