drop historical section number as was done in ps

Add, correct, and improve HISTORY sections.
From Sevan Janiyan <venture37 at geeklan dot co dot uk>.
Verified using http://minnie.tuhs.org/.

Document behavior of killing process 0, matching the text in kill(2).
From Theo Buehler

jmc@ found another manpage i broke when i touched inetd.

use kill -HUP 1 as an example of a hangup signal that does something
useful and non-contrived.

ok jmc@

note that the last two usage forms are marked xsi; ok millert

document EXIT STATUS; based on a diff from Daniel Dickman
ok millert

bump the posix reference in STANDARDS to IEEE Std 1003.1-2008, with a few
updates to follow;

i saw the previous was wrong as soon as i committed it: put the
built-in blurb in STANDARDS; we did once have a COMPATIBILITY section
which we merged with STANDARDS, so i think this is appropriate. i

i saw the previous was wrong as soon as i committed it: put the
built-in blurb in STANDARDS; we did once have a COMPATIBILITY section
which we merged with STANDARDS, so i think this is appropriate. it
certainly feels better than adding single sentences randomly to the
end of text bodies.

show more ...

document, consistently, those apps which also exist as built-ins
on certain shells; do not try to document changes between the
implementations, but at least warn of their existence;

diff from Ingo S

document, consistently, those apps which also exist as built-ins
on certain shells; do not try to document changes between the
implementations, but at least warn of their existence;

diff from Ingo Schwarze

show more ...

there is a reason why the argument to -l is "exit_status": as well as
showing the names of signals, it may also convert the exit status of
commands terminated by signals to their names. flesh out the

there is a reason why the argument to -l is "exit_status": as well as
showing the names of signals, it may also convert the exit status of
commands terminated by signals to their names. flesh out the description
of -l accordingly.

issue spotted by

show more ...

the ellipsis is not an optional argument; while here, sync the usage
and synopsis of commands

lots of good ideas by jmc@

ok jmc@

convert to new .Dd format;

- consistent STANDARDS blurb
- note which options are extensions to POSIX

discussed w/ deraadt otto millert

sort the options list; from Igor Sobrado

- more consistent macros
- descriptions of examples before examples, and indent examples
- direct people to sigaction(2) for complete list of signals
- .Xr pkill 1
- simplify a list

from jared yanov

- more consistent macros
- descriptions of examples before examples, and indent examples
- direct people to sigaction(2) for complete list of signals
- .Xr pkill 1
- simplify a list

from jared yanovich, and some bits from me;

show more ...

.br workaround no longer necessary;

- kill exists as a built-in to most shells, not just csh
- .Xr sh 1

ok millert@

Remove the advertising clause in the UCB license which Berkeley
rescinded 22 July 1999. Proofed by myself and Theo.

more .Li

use $ or # before commands in examples

document pgid usage; ok millert@

Initial patch.
When you give command examples in a manual page prefix them with
$ command
or
# command

deraadt@ ok

as early as v3 it seems to be

this both were in v4, before v6

Fix an incorrect example, reported by Gaël Queri <gqueri@mail.dotcom.fr>