Missing SIGPOLL and SIGPWR signals on some systems

[lifo101]

Missing SIGPOLL and SIGPWR signals on some systems

[lifo101]

One work-around, for now, is to overload the Daemon#setupSignals method and do not call getSignals. Instead just build your own list of signals to process. Those signals must have been removed in v5.6? The environment I'm using this daemon code in is still v5.4.

I suppose the getSignals method could be changed to protected instead of private to allow for overloading.

[npub]

Those signals must have been removed in v5.6?

Output of kill -l command:

macOS 10.13

1 ) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL
5 ) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE
9 ) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS
13 ) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGURG
17 ) SIGSTOP 18) SIGTSTP 19) SIGCONT 20) SIGCHLD
21 ) SIGTTIN 22) SIGTTOU 23) SIGIO 24) SIGXCPU
25 ) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH
29 ) SIGINFO 30) SIGUSR1 31) SIGUSR2

FreeBSD 10-11

HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM URG STOP TSTP CONT CHLD TTIN TTOU IO XCPU XFSZ VTALRM PROF WINCH INFO USR1 USR2 LWP

Seems like these signals are absent at all in that systems.

I suppose the getSignals method could be changed to protected instead of private to allow for overloading.

Changing to private works :)

And Daemon::setupSignals is better solution and will be great!

[npub]

Another way is to using of defined function to check all known signals before using.

if (defined('SIGPOLL')) {
    // do smth
}

[lifo101]

Another way is to using of defined function to check all known signals before using.

Yeah, I thought of that. Would just need to change the constants in getSignals to strings instead.