> Ah, it's probably doing a sigsuspend(2). I doubt it. That ties up your process/thread waiting for a signal. If you want to wait for IO, there are simpler ways.
My guess was sigprocmask(2). They way that I discovered that somebody was masking SIGINT was using it to read the current mask. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
