Your message dated Sun, 3 Jan 2016 12:09:43 +1100
with message-id <[email protected]>
and subject line Fixed in 3.3.10
has caused the Debian Bug report #673293,
regarding [kill] Improve kill.1 manpage for process groups
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.)
--
673293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673293
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: procps
Version: 1:3.3.2-3
Severity: normal
Dear Maintainer,
the documentation for /bin/kill does not state how to properly kill
process group. It mentions negative PID value may be used, but it
fails to mention the PID must be separated from signal number using
"--".
RHEL man page describe this better (IMHO):
"When an argument of the form -n is given, and it is meant to denote
a process group, either the signal must be specified first, or the
argument must be preceded by a -- option, otherwise
it will be taken as the signal to send."
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
(ignored: LC_ALL set to sk_SK.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages procps depends on:
ii initscripts 2.88dsf-22.1
ii libc6 2.13-32
ii libncurses5 5.9-7
ii libncursesw5 5.9-7
ii libprocps0 1:3.3.2-3
ii libtinfo5 5.9-7
ii lsb-base 4.1+Debian3
Versions of packages procps recommends:
ii psmisc 22.16-1
procps suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: procps
Version: 2:3.3.10-1
Hi,
Sorry I missed this in the changelog but kills parser got reworked in
3.3.10 which fixed this and other oddities. I tested it on 3.3.10-4
and things like /bin/kill -SUGHUP -99 work 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 ---
