Author gvanrossum
Recipients christian.heimes, gvanrossum, martius, neologix, vstinner, yselivanov
Date 2015-05-26.18:03:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJLaK=Tf77389W3zi4rjfAZOwJ9nFOJL24bHNcEpozce3g@mail.gmail.com>
In-reply-to <1432663268.89.0.615264296464.issue21998@psf.upfronthosting.co.za>
Content
That's really the problem of the code that calls fork(), not directly of
the event loop. There are some very solid patterns around that (I've
written several in the distant past, and Unix hasn't changed that much :-).

On Tue, May 26, 2015 at 11:01 AM, Yury Selivanov <report@bugs.python.org>
wrote:

>
> Yury Selivanov added the comment:
>
> > I don't understand. If the fork fails nothing changes right? I guess I'm
> missing some context or use case.
>
> Maybe I'm wrong about this.  My line of thoughts is: a failed fork() call
> is a bug in the program.  Now, the master process will continue operating
> as it was, no warnings, no errors.  The child process will crash with a
> RuntimeError exception.  Will it be properly reported/logged?
>
> I guess the forked child will share the stderr, so the exception won't
> pass completely unnoticed, right?
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue21998>
> _______________________________________
>
History
Date User Action Args
2015-05-26 18:03:16gvanrossumsetrecipients: + gvanrossum, vstinner, christian.heimes, neologix, yselivanov, martius
2015-05-26 18:03:16gvanrossumlinkissue21998 messages
2015-05-26 18:03:16gvanrossumcreate