-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/25/2014 04:15 PM, Iñaki Baz Castillo wrote:
> Hi,
> 
> Typically when handling signal interrupts the signal handler MUST
> NOT write into sockets or do stuff other than setting some
> variable.
> 

All i/o operations in libuv handle EINTR, and usually retry.

> Is it different when using the UV signal API? This is, is it safe
> to do any stuff in the signal_cb?
> 

You can do anything you want in the signal callback, it's safe.

> BTW I just want to handle SIGUSR1 in the UV loop of thread-1, while
> in other threads I block SIGUSR1 by using
> pthread_sigmask(SIG_BLOCK...). Is this OK if I use uv_signal in
> thread-1 to handle that signal?
> 
> Thanks a lot.
> 

Do your other threads also have libuv loops? In that case it would be
easier to just add a dummy signal handle for SIGUSR1 everywhere. I
think you should be fine though.


- -- 
Saúl Ibarra Corretgé
bettercallsaghul.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBAgAGBQJTgmKQAAoJEEEOVVOum8BZk54QAM/TwK8DSp2Zuod7TJOabN48
JhbhSI63H5298c0haQXAf+mtc88hpqoTvyPib+vfcxnqz7aDuKmaKZiWzhsHhFCr
ckXli4JvaIa6TOUqgyUMSvg8KbF0efFH8lUMB7pRhpTWn+haMlohXGz09SUfqG3Q
pxrJltRC6ikgzynaY2m7l+0/6GNl+EX5GFokei80GyD2imFMs9GVvxdieX8uaKFD
TUD/tmOVIvfIWqYPw6pQPl7TyVycoz+knjRSG+eipo64XaDQWoyNdJGvTsRAnlze
5/vbczBCJHJkwpH9cIh+a2RCIPIUK7xNrlzGRS/dCLPskDRNt5DlHXIqzpVYWP1s
IMlV/I2lzydUqXY64qllz9XSmA5P5ewXnyJXg85a9fqq4nIbPkFYksw4dG/8EJgk
i0omfKPyH5B/xGPiZkZSs5cLK5IF6Qnqb8pWklVZCYYsyzSicGc4unLkErZ0hyjo
nmD7uX9S3fQkvF0uzKWdzbIsid8uzrzvZXTBtmAsM98vWaP+WBmD9xW/eD8IVMPn
fJP88dcs+rtWW1hKeLrkY1vzSGygB/ikmQEd9t+Wa8utSqFIugaRzN/cbFbJzYiq
SCaBS01kmR5XpvIbfjL7dFLAFSL1TO7WMW5JRWne51jVTfA3rX0BJcl1vimYVKfj
I4I0WQw9XXpl6Wm6v0gV
=sTJo
-----END PGP SIGNATURE-----

-- 
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.

Reply via email to