Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#30372 - [psmisc] killall=OVERKILL

Attached to Project: Arch Linux
Opened by Natrio (natrio) - Wednesday, 20 June 2012, 07:08 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 20 June 2012, 09:17 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


In psmisc-22.18-1 killall (without any parameters) kills REALLY everything.

How to reproduce:
1) Be shure you have psmisc-22.18-1
2) Log in as root
3) killall
4) Enjoy :)

In previous versions:
$ killall
Usage: killall [OPTION]... [--] NAME...
killall -l, --list
killall -V, --version

-e,--exact require exact match for very long names
-I,--ignore-case case insensitive process name match
-g,--process-group kill process group instead of process
-y,--younger-than kill processes younger than TIME
-o,--older-than kill processes older than TIME
-i,--interactive ask for confirmation before killing
-l,--list list all known signal names
-q,--quiet don't print complaints
-r,--regexp interpret NAME as an extended regular expression
-s,--signal SIGNAL send this signal instead of SIGTERM
-u,--user USER kill only process(es) running as USER
-v,--verbose report if the signal was successfully sent
-V,--version display version information
-w,--wait wait for processes to die
This task depends upon

Closed by  Eric Belanger (Snowman)
Wednesday, 20 June 2012, 09:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  psmisc-22.18-2
Comment by Thomas B├Ąchler (brain0) - Wednesday, 20 June 2012, 08:47 GMT
Actually, 'killall' only seems to kill the current login shell and its subprocesses. However, when you run it during system shutdown or reboot, it really kills everything.
Comment by Natrio (natrio) - Wednesday, 20 June 2012, 08:53 GMT
Yes, as user it not so powerfull :)
Comment by Natrio (natrio) - Wednesday, 20 June 2012, 08:54 GMT
I posted bug report to the upstream, but perhaps as long as they are correct, it is worth while to roll back?
Comment by Eric Belanger (Snowman) - Wednesday, 20 June 2012, 08:54 GMT
For reference, upstream bug report:

If you give it a wrong option, it also kills everythings. I accidentally killed my X session when I ran "killall --help" when investigating this bug.