access(2) alarm(2) pause(2) were not ported from pwb to v7

Alan Glasser describes the incident that led to access(2) in
https://minnie.tuhs.org/pipermail/tuhs/2021-November/024657.html

access(2) alarm(2) pause(2) were also part of the "50 changes" tape

post v6 "50 bugs" / "diff tape" / "50 fixes" tape (Salus QCU, pp 138-139)
"fifty changes" tape
https://www.oreilly.com/openbook/opensources/book/kirkmck.html

"50 changes"
https://archive.org/details/unix_news_november-1976

tuhs/Applications/Spencer_Tapes/unsw3.tar.gz
usr/sys/v6unix/changenotes

45) The "access()" system call checks access permissions on the real
id's of the process regardless of the effective ones. Doesn't return
stats, just does an internal "access()" to set u.u_error.

48) "alarm()" and "pause()" system calls are in to provide a user-mode
timeout capability.

with and ok schwarze@

alarm.3: miscellaneous improvements to alarm(3) documentation

Improve the alarm(3) manpage:

- Better one-line description of the interface.

- Carefully describe what alarm(3) actually does. In particular, the
first paragraph of the current DESCRIPTION is misleading in several
ways.

- Remove mention of the 100 million second limit. As of kern_time.c v1.154,
setitimer(2) no longer has this limit on OpenBSD.

- An alarm is "pending" if it has been scheduled but has not yet
"expired".

- Rewrite RETURN VALUES. Remind the reader that calling alarm(3)
cancels any pending alarm. Enumerate all the cases where alarm(3)
could return zero.

- Remove all descriptions of errors and errno. With the removal of
the 100 million second limit, alarm(3) basically cannot fail on
OpenBSD unless the stack is corrupted.

Unfortunately, the standard does not prescribe a portable return
value to report an error to the caller.

- Add a CAVEATS section. Discourage use of alarm(3) and setitimer(2)'s
ITIMER_REAL timer in the same program.

With input from millert@, deraadt@, and jmc@.

Thread: https://marc.info/?l=openbsd-tech&m=162403868814857&w=2

ok millert@, jmc@

sigsuspend is section 2, not 3.

The CSRG declared alarm(3) obsolete 30 years ago (before 4.2BSD),
but it is likely to remain in POSIX for the forseeable future,
and there is nothing wrong with using it, so remove the marker.
By contrast, POSIX 2008 now declared setitimer(3) obsolescent.

While here, remove a few cross references pointing to obsolete or
non-standard functions and update the POSIX reference.

Triggered by a question from <ChrisBennett at bennettconstruction dot us>.
OK millert@ tb@

more library history
facts checked by sobrado@
style tweaks and ok jmc@

Use the fancy .In macro for includes. From Jan Klemkow. ok jmc schwarze

convert to new .Dd format;

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

Add RETURN VALUES section
Max alarm time is 100000000 seconds, not 2147483647 (as enforced by
itimerfix() in kern_time.c)

Various repairs, mostly to get rid of short lines.

- remove all trailing whitespace
* except when it is escaped with a `\' at the end of the line
- fix remaining .Nm usage as well
- this is from a patch I received from kwesterback@home.com, who has been
working on some scripts for fixing formatting errors in mdoc'd man pages

Ok, so there could be a cost/benefit debate with this commit, but since I have
the patch we might as well commit it...

remove argument from .Os macros so value in /usr/share/tmac/mdoc/doc-common
is used instead; kwesterback@home.com

Cleanup xrefs under SEE ALSO. Specifically:

- Sort xrefs by section, and then alphabetically.
- Add missing commas between xref items.
- Remove commas from the last xref entry.
- Remove duplicate entries.

correct some Xr's which referred to the wrong man page sections

use Xr more often

Fix RCS ids
Make sure everything uses {SYS,}LIBC_SCCS properly

branches: 1.1.1;
Initial revision

alarm.3: miscellaneous improvements to alarm(3) documentation

Improve the alarm(3) manpage:

- Better one-line description of the interface.

- Carefully describe what alarm(3) actually does. In particular, the
first paragraph of the current DESCRIPTION is misleading in several
ways.

- Remove mention of the 100 million second limit. As of kern_time.c v1.154,
setitimer(2) no longer has this limit on OpenBSD.

- An alarm is "pending" if it has been scheduled but has not yet
"expired".

- Rewrite RETURN VALUES. Remind the reader that calling alarm(3)
cancels any pending alarm. Enumerate all the cases where alarm(3)
could return zero.

- Remove all descriptions of errors and errno. With the removal of
the 100 million second limit, alarm(3) basically cannot fail on
OpenBSD unless the stack is corrupted.

Unfortunately, the standard does not prescribe a portable return
value to report an error to the caller.

- Add a CAVEATS section. Discourage use of alarm(3) and setitimer(2)'s
ITIMER_REAL timer in the same program.

With input from millert@, deraadt@, and jmc@.

Thread: https://marc.info/?l=openbsd-tech&m=162403868814857&w=2

ok millert@, jmc@

sigsuspend is section 2, not 3.

The CSRG declared alarm(3) obsolete 30 years ago (before 4.2BSD),
but it is likely to remain in POSIX for the forseeable future,
and there is nothing wrong with using it, so remove the marker.
By contrast, POSIX 2008 now declared setitimer(3) obsolescent.

While here, remove a few cross references pointing to obsolete or
non-standard functions and update the POSIX reference.

Triggered by a question from <ChrisBennett at bennettconstruction dot us>.
OK millert@ tb@

more library history
facts checked by sobrado@
style tweaks and ok jmc@

Use the fancy .In macro for includes. From Jan Klemkow. ok jmc schwarze

convert to new .Dd format;

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

Add RETURN VALUES section
Max alarm time is 100000000 seconds, not 2147483647 (as enforced by
itimerfix() in kern_time.c)

Various repairs, mostly to get rid of short lines.

- remove all trailing whitespace
* except when it is escaped with a `\' at the end of the line
- fix remaining .Nm usage as well
- this is from a patch I received from kwesterback@home.com, who has been
working on some scripts for fixing formatting errors in mdoc'd man pages

Ok, so there could be a cost/benefit debate with this commit, but since I have
the patch we might as well commit it...

remove argument from .Os macros so value in /usr/share/tmac/mdoc/doc-common
is used instead; kwesterback@home.com

Cleanup xrefs under SEE ALSO. Specifically:

- Sort xrefs by section, and then alphabetically.
- Add missing commas between xref items.
- Remove commas from the last xref entry.
- Remove duplicate entries.

correct some Xr's which referred to the wrong man page sections

use Xr more often

Fix RCS ids
Make sure everything uses {SYS,}LIBC_SCCS properly

branches: 1.1.1;
Initial revision

sigsuspend is section 2, not 3.

The CSRG declared alarm(3) obsolete 30 years ago (before 4.2BSD),
but it is likely to remain in POSIX for the forseeable future,
and there is nothing wrong with using it, so remove the marker.
By contrast, POSIX 2008 now declared setitimer(3) obsolescent.

While here, remove a few cross references pointing to obsolete or
non-standard functions and update the POSIX reference.

Triggered by a question from <ChrisBennett at bennettconstruction dot us>.
OK millert@ tb@

more library history
facts checked by sobrado@
style tweaks and ok jmc@

Use the fancy .In macro for includes. From Jan Klemkow. ok jmc schwarze

convert to new .Dd format;

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

Add RETURN VALUES section
Max alarm time is 100000000 seconds, not 2147483647 (as enforced by
itimerfix() in kern_time.c)

Various repairs, mostly to get rid of short lines.

- remove all trailing whitespace
* except when it is escaped with a `\' at the end of the line
- fix remaining .Nm usage as well
- this is from a patch I received from kwesterback@home.com, who has been
working on some scripts for fixing formatting errors in mdoc'd man pages

Ok, so there could be a cost/benefit debate with this commit, but since I have
the patch we might as well commit it...

remove argument from .Os macros so value in /usr/share/tmac/mdoc/doc-common
is used instead; kwesterback@home.com

Cleanup xrefs under SEE ALSO. Specifically:

- Sort xrefs by section, and then alphabetically.
- Add missing commas between xref items.
- Remove commas from the last xref entry.
- Remove duplicate entries.

correct some Xr's which referred to the wrong man page sections

use Xr more often

Fix RCS ids
Make sure everything uses {SYS,}LIBC_SCCS properly

branches: 1.1.1;
Initial revision