Your message dated Thu, 29 Jan 2015 22:06:02 +1100 with message-id <[email protected]> and subject line Re: Bug#776266: procps: Killing process groups is broken has caused the Debian Bug report #776266, regarding procps: Killing process groups is broken to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 776266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776266 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: procps Version: 1:3.3.3-3 Severity: normal This works as documented by "man kill", using the bash kill built-in: ~$ ( yes | ts > foo ) & [3] 8950 ~$ echo $! 8950 ~$ kill -s 15 -$! ~$ And here is what /bin/kill does (which, of course, is actually what "man kill" purports to describe): ~$ ( yes | ts > foo ) & [4] 9082 ~$ ps x | fgrep yes | fgrep -v fgrep 9083 pts/0 S 0:00 yes ~$ /bin/kill -s 15 -$! /bin/kill: invalid option -- '9' Usage: kill [options] <pid> [...] Options: <pid> [...] send signal to every <pid> listed -<signal>, -s, --signal <signal> specify the <signal> to be sent -l, --list=[<signal>] list all signal names, or convert one to a name -L, --table list all signal names in a nice table -h, --help display this help and exit -V, --version output version information and exit For more details see kill(1). ~$ ps x | fgrep yes | fgrep -v fgrep 9083 pts/0 S 0:00 yes -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.10.65.5 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages procps depends on: ii initscripts 2.88dsf-41+deb7u1 ii libc6 2.13-38+deb7u6 ii libncurses5 5.9-10 ii libncursesw5 5.9-10 ii libprocps0 1:3.3.3-3 ii libtinfo5 5.9-10 ii lsb-base 4.1+Debian8+deb7u1 Versions of packages procps recommends: ii psmisc 22.19-1+deb7u1 procps suggests no packages. -- Configuration Files: /etc/sysctl.conf changed [not included] -- no debconf information
--- End Message ---
--- Begin Message ---Package: procps Version: 1:3.3.4-1 On Sun, Jan 25, 2015 at 07:00:05PM -0800, Ian Zimmerman wrote: > And here is what /bin/kill does (which, of course, is actually what "man > kill" purports to describe): Hi Ian, This is a duplicate of Debian bug #688731 and was fixed in upstream version 3.3.4 Thanks for the test situations though, they are handy to check things are really fixed. The relevant git commit was: Author: Craig Small <[email protected]> Date: Tue Oct 2 21:56:38 2012 +1000 kill -PID fixed Bug-Debian: http://bugs.debian.org/688731 kill would not permit negative PIDs and thought they were options. kill now explicitly checks for unknown options and if they are numeric assumes they are negative PIDs. The first negative PID stops any further option processing. Signed-off-by: Craig Small <[email protected]> I've checked my version (3.3.9-8) and it works correctly. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
--- End Message ---
