| created | 2021-06-20T20:16:56Z |
|---|---|
| begin | 2021-06-18T15:34:21Z |
| end | 2021-06-18T15:59:14Z |
| path | src/sys |
| commits | 1 |
| date | 2021-06-18T15:59:14Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_time.c | log | diff | annotate |
| message |
setitimer(2): increase timer limit to UINT_MAX seconds Currently setitimer(2) rejects timers larger than 100 million seconds and sets EINVAL. With the change to kclock timeouts there is no longer any reason to use this arbitrary value. Kclock timeouts support the full range of a timespec, so we can increase the upper bound without practical risk of arithmetic overflow. If we push the limit to UINT_MAX we can support the full input range of alarm(3). We can then simplify the alarm.3 manpage in a separate patch. We can push the limit even higher in the future if we find software that doesn't like the UINT_MAX limit. Until then, UINT_MAX seconds (over 68 years) is plenty for all practical timers. ok claudio@ |
|||