From 9cd6f02395b5420d72e36ecadb612fc5b1537e56 Mon Sep 17 00:00:00 2001 From: Nihal Jere Date: Fri, 19 Feb 2021 15:04:06 -0600 Subject: [PATCH 1/2] ignore real-time signals by default, unless explicitly set --- dwmblocks.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/dwmblocks.c b/dwmblocks.c index 68267d7..18f58fb 100644 --- a/dwmblocks.c +++ b/dwmblocks.c @@ -111,6 +111,10 @@ void getsigcmds(int signal) void setupsignals() { struct sigaction sa; + + for(int i = SIGRTMIN; i <= SIGRTMAX; i++) + signal(i, SIG_IGN); + for(int i = 0; i < LENGTH(blocks); i++) { if (blocks[i].signal > 0) From c9e45f9bed6fa44a7d0e29e4aee8ba93297d0cc0 Mon Sep 17 00:00:00 2001 From: Nihal Jere Date: Fri, 19 Feb 2021 15:10:38 -0600 Subject: [PATCH 2/2] update README.md --- README.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/README.md b/README.md index 2b40431..7d21e30 100644 --- a/README.md +++ b/README.md @@ -31,11 +31,7 @@ but is faster. Just add 34 to your typical signal number. My volume module *never* updates on its own, instead I have this command run along side my volume shortcuts in dwm to only update it when relevant. -Note that if you signal an unexpected signal to dwmblocks, it will probably -crash. So if you disable a module, remember to also disable any cronjobs or -other scripts that might signal to that module. - -Note also that all modules must have different signal numbers. +Note that all modules must have different signal numbers. # Clickable modules