I can no longer use the signals SIGUSR1 and SIGUSR2 in my programs! Why?

最新推荐文章于 2021-09-26 01:10:12 发布

hongtoushiziyuan

最新推荐文章于 2021-09-26 01:10:12 发布

阅读量133

点赞数

分类专栏： linux 文章标签： nodejs

本文链接：https://blog.csdn.net/sifeimeng/article/details/84737737

版权

linux 专栏收录该内容

20 篇文章 0 订阅

订阅专栏

(1):

H.4: With LinuxThreads, I can no longer use the signals `SIGUSR1` and `SIGUSR2` in my programs! Why?

The short answer is: because the Linux kernel you're using does not support realtime signals.

LinuxThreads needs two signals for its internal operation. One is used to suspend and restart threads blocked on mutex, condition or semaphore operations. The other is used for thread cancellation.

On ``old'' kernels (2.0 and early 2.1 kernels), there are only 32 signals available and the kernel reserves all of them but two: SIGUSR1 and SIGUSR2. So, LinuxThreads has no choice but use those two signals.

On recent kernels (2.2 and up), more than 32 signals are provided in the form of realtime signals. When run on one of those kernels, LinuxThreads uses two reserved realtime signals for its internal operation, thus leaving SIGUSR1 and SIGUSR2 free for user code. (This works only with glibc, not with libc 5.)

(2)

USR1亦通常被用来告知应用程序重载配置文件；例如，向Apache HTTP服务器发送一个USR1信号将导致以下步骤的发生：停止接受新的连接，等待当前连接停止，重新载入配置文件，重新打开日志文件，重启服务器，从而实现相对平滑的不关机的更改。

摘自： http://pauillac.inria.fr/~xleroy/linuxthreads/faq.html#H.4