The GNU Bourne-Again SHell - Patches: patch #8025, Obsolete SIGRTMAX-n signal names
You are not allowed to post comments on this tracker with your current authentication level.
patch #8025: Obsolete SIGRTMAX-n signal names
Submitter: | Harald Hoyer <haraldhoyer> | ||
Submitted: | Fri 19 Apr 2013 05:59:32 AM UTC | ||
Category: | None | Priority: | 5 - Normal |
Status: | Done | Privacy: | Public |
Assigned to: | None | Open/Closed: | Open |
Attached Files
file #27910: 0001-Obsolete-SIGRTMAX-n-signal-names.patch added by haraldhoyer (7KiB - text/x-patch - patch)
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-10-19 | chet | Status | None | Done | |
2013-04-19 | haraldhoyer | Attached File | - | Added 0001-Obsolete-SIGRTMAX-n-signal-names.patch, #27910 |
Powered by Savane 3.13-f8d8.
Corresponding source code
Never ever address signals with SIGRTMAX-n. Signals should always be addressed with SIGRTMIN+n.
http://man7.org/linux/man-pages/man7/signal.7.html
[...]
programs should never refer to real-time signals using hard-coded numbers, but instead should always refer to real-time signals using the notation SIGRTMIN+n
[...]
This patch makes the SIGRTMIN+n notation the default, but understands the old SIGRTMAX-n notation as well.