On 29/12/2025 21:53, Collin Funk wrote:
Pádraig Brady <[email protected]> writes:Well all of the above is testing kill(1), and posix doesn't specify name -> number support, so I'm not sure framework_failure is appropriate here. Couldn't we just exclude kill(1) here. I.e., not do any of the above, and just pass "RTMIN' and "RTMAX" to env, like: if test $SIGRTMIN -gt 0 && test $SIGRTMAX -gt $SIGRTMIN; then for sig in 'RTMIN' 'RTMAX'; do ... done fiPOSIX requires that the range SIGRTMIN to SIGRTMAX are reserved for real-time signals, not that any of them (including SIGRTMIN and SIGRTMAX) are supported signal numbers. So that code just finds the highest and lowest and uses them. That is probably a theoretical issue, though. Let me do some experimenting on the cfarm machines to check if SIGRTMIN and SIGRTMAX are valid signal numbers.
Right. I can't see that if they're defined, they wouldn't be supported.
BTW, that file uses require_bash_as_SHELL_. So we should be getting the 'kill' builtin from bash. Maybe some old versions don't support that syntax though, I am not sure.
Oh right. That deserves a comment at least. Also we could rely on the fact that if bash supports `kill -l RTMIN RTMAX`, then env should be able to support those names, though it's probably fine for env to use those names once the defines are present. cheers, Padraig.
