Message 244118 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	yselivanov
Recipients	christian.heimes, gvanrossum, martius, neologix, vstinner, yselivanov
Date	2015-05-26.18:01:08
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
> 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?

> 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?

History
Date	User	Action	Args
2015-05-26 18:01:08	yselivanov	set	recipients: + yselivanov, gvanrossum, vstinner, christian.heimes, neologix, martius
2015-05-26 18:01:08	yselivanov	set	messageid: <[email protected]>
2015-05-26 18:01:08	yselivanov	link	issue21998 messages
2015-05-26 18:01:08	yselivanov	create