GNURLOPT_NOSIGNAL(3)

💅 GNURLOPT_NOSIGNAL(3) 💅

okay so bestie, this page lives in the curl_easy_setopt options manual, and we are talking about the icon that is CURLOPT_NOSIGNAL — literally the "skip all signal handling" option. no cap, it's giving safety-for-threaded-girlies energy 🫶

---

✨ NAME ✨

CURLOPT_NOSIGNAL — skip all signal handling 💅

---

🦋 SYNOPSIS 🦋

#include <gnurl/curl.h>

CURLcode curl_easy_setopt(CURL *handle, CURLOPT_NOSIGNAL, long onoff);

---

🌸 DESCRIPTION 🌸

okay so if onoff is 1, libcurl will not use any functions that install signal handlers, and it will not use any functions that cause signals to be sent to the process. that's the whole vibe ✨

this option is here so multi-threaded unix applications can still set/use all timeout options etc, without risking getting signals. main character energy for your threads, honestly 🧚

if this option is set and libcurl has been built with the standard name resolver, timeouts will not occur while the name resolve takes place. so consider building libcurl with the c-ares or threaded resolver backends to enable asynchronous DNS lookups — that way you get timeouts for name resolves without the use of signals. lowkey important, bestie 🎀

setting CURLOPT_NOSIGNAL(3) to 1 makes libcurl NOT ask the system to ignore SIGPIPE signals. those are otherwise sent by the system when trying to send data to a socket which is closed in the other end 😭 libcurl makes an effort to never cause such SIGPIPEs to trigger, but some operating systems have no way to avoid them — and even on those that have, there are some corner cases when they may still happen, contrary to our desire. fr fr, it's not personal 💀

in addition, using CURLAUTH_NTLM_WB authentication could cause a SIGCHLD signal to be raised. just so you know 👑

---

🍓 DEFAULT 🍓

0

---

🌈 AVAILABILITY 🌈

added in 7.10 ⭐

---

💖 RETURN VALUE 💖

returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not. slay 🫶

---

mwah 💋 this lil page is from libcurl 7.37.0, dated 16 Jun 2014 — and yes, it's still GNURLOPT_NOSIGNAL(3) coded, bestie. go forth and handle your signals (or don't, that's literally the point) ✨🎀💅