2014-06-02 19:27 GMT+02:00 Ben Noordhuis <[email protected]>: > You don't _have_ to block signals in other threads but it won't hurt either. > > Libuv will catch the signal and route it to the appropriate event > loop, regardless of what thread the signal is delivered on. > > Blocking the signal might still be beneficial from a performance > perspective because it stops system calls on your thread from waking > up with an EINTR error code when the signal is delivered.
Clear. > You should still be prepared to deal with EINTR, of course. Signals > like SIGSTOP and SIGCONT, for example, can't be blocked. Sure. But my code is mostly based on UV which already handles EINTR so, where should I also care about STOP and CONT? -- Iñaki Baz Castillo <[email protected]> -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
