<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

<html lang="en">

<head>

<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<p style="color: #777777;">

<a href="https://gitlab.com/rockdaboot">Tim Rühsen</a>

commented on a

<a href="https://gitlab.com/gnutls/gnutls/-/issues/985#note_348213844">discussion</a>:

</p>

<div style="">

<blockquote dir="auto">

<p>But that is a red herring: The problem is not fork() here. The problem comes with exec() family functions</p>

</blockquote>

<p dir="auto">Yes, you are right, fork and exec are two different pais of shoes. Forking a MT application needs application logic to deal with e.g. write-open files (not suddenly having two processes writing into the same file). And that is a different issue than the exec() one, leaking file descriptors.</p>

</div>

</div>

<div class="footer" style="margin-top: 10px;">

<p style="font-size: small; color: #777;">

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/-/issues/985#note_348213844">view it on GitLab</a>.

<br>

You're receiving this email because of your account on gitlab.com.

If you'd like to receive fewer emails, you can

<a href="https://gitlab.com/-/sent_notifications/e45ff2982b328c67808b2590abb7e039/unsubscribe">unsubscribe</a>

from this thread or

adjust your notification settings.

<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Issue","url":"https://gitlab.com/gnutls/gnutls/-/issues/985#note_348213844"}}</script>

</p>

</div>

</body>

</html>