New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libcurl-thread.3: expand somewhat on the NO_SIGNAL motivation #2904

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
1 participant
@bagder
Member

bagder commented Aug 21, 2018

Multi-threaded applictions basically MUST set CURLOPT_NO_SIGNAL to 1L to
avoid the risk of getting a SIGPIPE.

Either way, a multi-threaded application that uses libcurl/openssl needs
to have a signhandler for or ignore SIGPIPE on its own.

Based on discussions in #2800

/cc @linusnielsen @yandreiy @ThomasObenaus

libcurl-thread.3: expand somewhat on the NO_SIGNAL motivation
Multi-threaded applictions basically MUST set CURLOPT_NO_SIGNAL to 1L to
avoid the risk of getting a SIGPIPE.

Either way, a multi-threaded application that uses libcurl/openssl needs
to have a signhandler for or ignore SIGPIPE on its own.

Based on discussions in #2800

@bagder bagder closed this in 1b8ed4a Aug 23, 2018

@bagder bagder deleted the bagder/docs-threaded-SIGPIPE branch Aug 23, 2018

falconindy added a commit to falconindy/curl that referenced this pull request Sep 10, 2018

libcurl-thread.3: expand somewhat on the NO_SIGNAL motivation
Multi-threaded applictions basically MUST set CURLOPT_NO_SIGNAL to 1L to
avoid the risk of getting a SIGPIPE.

Either way, a multi-threaded application that uses libcurl/openssl needs
to have a signhandler for or ignore SIGPIPE on its own.

Based on discussions in curl#2800
Closes curl#2904

@lock lock bot locked as resolved and limited conversation to collaborators Nov 21, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.