coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] tests: env: check that real-time signals can be ignored


From: Collin Funk
Subject: Re: [PATCH] tests: env: check that real-time signals can be ignored
Date: Mon, 29 Dec 2025 13:53:41 -0800
User-agent: Gnus/5.13 (Gnus v5.13)

PƔdraig Brady <P@draigBrady.com> 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
> fi

POSIX 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.

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.

Collin



reply via email to

[Prev in Thread] Current Thread [Next in Thread]