|
in reply to LWP is not SIGPIPE safe?
One thing to remember is that SIGPIPE is global for that
program. So, after looking at your examples, my guess is that the authors each had different requirements. GAAS may not have wanted to use SIGPIPE because of its global implications
and requirements, and his usage of syswrite doesn't suggest that LWP isn't SIGPIPE safe. |
Re^2: LWP is not SIGPIPE safe?
by OlegG (Monk) on Nov 28, 2012 at 17:25 UTC
|
In HTTP::Tiny example "local $SIG{PIPE}" used, so it handles only sigpipe emitted from the block where it was installed.
May be lwp's syswrite is safe. But I want to know reason why it is safe. For example: syswrite() can't fail if it was called immediately after socket opening and data length for write is small enough. | [reply] |
|
