Terminal taking up 1/3 screen

Ralf Mardorf silver.bullet at zoho.com
Sun Jul 24 11:18:03 UTC 2016


On Sun, 24 Jul 2016 19:59:38 +1000, Karl Auer wrote:
>On Sun, 2016-07-24 at 11:17 +0200, Ralf Mardorf wrote:
>> On Sun, 24 Jul 2016 14:05:53 +1000, Karl Auer wrote:  
>> >   kill -TERM pid
>> >   killall -TERM bash  
>> 
>> JFTR by default signal 15, aka SIGTERM is send.  
>
>But by providing the parameter I also educate people by-the-way about
>the fact that signals are being sent and also about the possibility of
>other values.

For the sake of completeness IMO it's better to point out, that there's
no need to "remember" the default signal name, just running

  kill 1234

or

  killall foo

is enough. Assumed this shouldn't work, then -9 (KILL) or -w might be
required. I fear that beginners might not remember the default signal
name, so instead of "-TERM" they directly use "-KILL", since this might
be easier to remember.

2 cents,
Ralf

PS:

A default Ubuntu install might provide a shortcut to kill a GUI by
hovering the mouse cursor over the window and a simple left-click.

If not, this instruction might work:

  sudo apt-get update && sudo apt-get x11-utils

"You could create a keyboard shortcut for xkill.

    Type keyboard in the Unity Dash and click the icon. Select the
    shortcuts tab.

    There, scroll down to the custom shortcuts section and click on the
    + button

    Now name your shortcut something and let the command be xkill and
    then click ok. Finally click on the xkill shortcut and press the
    desired key-combo to assign a shortcut to it and that's it :)
    Pressing the keyboard shortcut will activate xkill whenever you
    need it." -
    http://askubuntu.com/questions/90773/how-to-kill-non-responsive-gui-task-under-unity




More information about the ubuntu-users mailing list