<!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/Courmisch">Remi Denis-Courmont</a>

commented on a

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

</p>

<div style="">

<p dir="auto"><code>fork()</code> is very limited in a multi-thread process. But that is a red herring:

The problem is not <code>fork()</code> here. The problem comes with <code>exec()</code> family functions, which leak file descriptors. If you call <code>exec()</code> directly, the problem exists all the same - it's just far more likely that <code>fork()</code> would occur first.</p>

<p dir="auto">And if you don't like the idea of calling <code>fork()</code> then <code>exec()</code> in a multi-thread process, you can imagine using a function from the <code>posix_spawn()</code> instead: same causes, same problem.</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_348103783">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/d38e782840b8a0dd3740689d8bcf7e58/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_348103783"}}</script>

</p>

</div>

</body>

</html>