summaryrefslogtreecommitdiff
path: root/sys/compat/linux/common/linux_socket.c
diff options
context:
space:
mode:
authorchristos <christos@NetBSD.org>2001-11-13 00:34:21 +0000
committerchristos <christos@NetBSD.org>2001-11-13 00:34:21 +0000
commitd1dcd2f4016cf797927e3c1b6d299e43366da8fd (patch)
treefeca599460b7eb1d26ce138da78f035781f94e51 /sys/compat/linux/common/linux_socket.c
parentea1cd7eb0877f959d6fc52877ba8b3da36a7eb1f (diff)
PR/8657: z@rentaboat.se: alarm takes more seconds that it can handle.
This is a followup to PR/14558. - itimerfix(9) limited the number of seconds to 100M, before I changed it to 1000M for PR/14558. - nanosleep(2) documents a limit of 1000M seconds. - setitimer(2), select(2), and other library functions that indirectly use setitimer(2) for example alarm(3) don't specify a limit. So it only seems appropriate that any positive number of seconds in struct timeval should be accepted by any code that uses itimerfix(9) directly, except nanosleep(2) which should check for 1000M seconds manually. This changes makes the manual pages of select(2), nanosleep(2), setitimer(2), and alarm(3) consistent with the code.
Diffstat (limited to 'sys/compat/linux/common/linux_socket.c')
0 files changed, 0 insertions, 0 deletions