Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #742
Difficulty: Medium
XL Fortran is the name of an open source Fortran compiler for IBM-supported environments, including Linux for big-endian distributions and AIX.
True or False?
Linux & Unix Commands - Search Man Pages

bosskill(8) [linux man page]

BOSSKILL(8)						      System Manager's Manual						       BOSSKILL(8)

NAME
bosskill - send a signal to your boss, or terminate your boss SYNOPSIS
bosskill [ -signal ] <bossname> DESCRIPTION
bosskill sends the TERM (terminate, 15) signal to the boss with the specified bossname. If a signal name or number preceded by `-' is given as the first argument, that signal is sent instead of terminate. The killed boss must be in the system administrator's supervisory chain. The following is a list of all signals with names as in the include file <signal.h>: SIGHUP 1 hangup. Forces bossname to re-read his/her job description and figure out that he/she knows squat about sysadmin work or life, in general. SIGINT 2 interrupt. Prevents the bossname from interrupting the sysadmin for one hour. SIGQUIT 3 quit. Causes the boss to quit his/her job with no explanation. SIGILL 4 illegal instruction. Makes the boss believe the last instruction he/she gave was illegal, so he/she withdraws it. SIGTRAP 5 trace trap. Display the exact location of the boss. SIGABRT 6 abort. Makes the boss go home and try again tomorrow. SIGKILL 9 kill. Game over. SIGBUS 10 bus error. Boss's transportation fails on the way to work. SIGSEGV 11 segmentation violation. Boss realizes he/she is trying to do something for which he/she is not quailified and stops. SIGSYS 12 bad argument. Boss loses. SIGPIPE 13 smoke pipe. Boss samples some green leafy substance and mellows out. SIGALRM 14 alarm. Boss is startled and falls over. Best used when boss is walking next to his/her boss. SIGTERM 15 termination signal. Boss is fired. BUGS
Sending a SIGABRT to a boss that is already home will cause him/her to walk aimlessly in circles for two hours. HISTORY
Written by Eric L. Pederson <eric@bofh.org.uk>. 27 September 1995 BOSSKILL(8)

Check Out this Related Man Page

KILL(1) 						    BSD General Commands Manual 						   KILL(1)

NAME
kill -- terminate or signal a process SYNOPSIS
kill [-s signal_name] pid ... kill -l [exit_status] kill -signal_name pid ... kill -signal_number pid ... DESCRIPTION
The kill utility sends a signal to the process(es) specified by the pid operand(s). Only the super-user may send signals to other users' processes. The options are as follows: -s signal_name A symbolic signal name specifying the signal to be sent instead of the default TERM. -l [exit_status] Display the name of the signal corresponding to exit_status. exit_status may be the exit status of a command killed by a signal (see the special sh(1) parameter '?') or a signal number. If no operand is given, display the names of all the signals. -signal_name A symbolic signal name specifying the signal to be sent instead of the default TERM. -signal_number A non-negative decimal integer, specifying the signal to be sent instead of the default TERM. The following pids have special meanings: -1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user. 0 Broadcast the signal to all processes in the current process group belonging to the user. Some of the more commonly used signals: 1 HUP (hang up) 2 INT (interrupt) 3 QUIT (quit) 6 ABRT (abort) 9 KILL (non-catchable, non-ignorable kill) 14 ALRM (alarm clock) 15 TERM (software termination signal) kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill argu- ments. See csh(1) for details. SEE ALSO
csh(1), pgrep(1), pkill(1), ps(1), kill(2), sigaction(2), signal(7) STANDARDS
The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible. HISTORY
A kill command appeared in Version 6 AT&T UNIX. BSD
April 28, 1995 BSD

Featured Tech Videos