summaryrefslogtreecommitdiff
path: root/src/kill.c
diff options
context:
space:
mode:
authorCraig Small <csmall@dropbear.xyz>2023-03-01 17:35:14 +1100
committerCraig Small <csmall@dropbear.xyz>2023-03-01 17:35:14 +1100
commit8c81808de09b034c5dc2221aacc85d25c3218676 (patch)
tree6c52ec3074a5be85c0de31f00ac3ccba42ed8579 /src/kill.c
parent9b2f49166b73cef360cff0682459a0aa3e6ec8d8 (diff)
downloadprocps-ng-8c81808de09b034c5dc2221aacc85d25c3218676.tar.gz
pgrep: Use only --signal option for signal
When pgrep was used to match on signal, it makes sense to use the same signal parsing code as pkill. Unfortunately the "find the signal" part is a little too enthusaistic about what a signal is, meaning pgrep -u -42 fails because the signal becomes "42" and then there is no UID. This is a bit sad for pkill but has been that way for a long time. For pgrep this is new so now only the long form pgrep --signal <X> will work. In addition, when using --signal if pgrep/pkill couldn't work out what the signal was it just silently ignored it. It now complains and aborts. References: https://bugs.debian.org/1031765 commit 866abacf8805a74fb7c59cae1f64963e0a540b14
Diffstat (limited to 'src/kill.c')
0 files changed, 0 insertions, 0 deletions