summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBrian Inglis <Brian.Inglis@Shaw.ca>2023-02-08 13:27:25 -0700
committerAlejandro Colomar <alx@kernel.org>2023-02-12 20:23:53 +0100
commit147a60d792a5db8f3cb93ea16eefb73e16c1fb91 (patch)
tree592481f61267f2463af48474f6c9a9664b1a0f96
parent0c99abfde5313a25f8c4978ad6dfb9c02788c559 (diff)
man2/: use consistent closed interval notation for value ranges
Signed-off-by: Alejandro Colomar <alx@kernel.org>
-rw-r--r--man2/clock_getres.22
-rw-r--r--man2/clock_nanosleep.22
-rw-r--r--man2/getitimer.24
-rw-r--r--man2/gettimeofday.22
-rw-r--r--man2/nanosleep.24
-rw-r--r--man2/utimensat.22
6 files changed, 8 insertions, 8 deletions
diff --git a/man2/clock_getres.2 b/man2/clock_getres.2
index c10f980fa..8d90baaaa 100644
--- a/man2/clock_getres.2
+++ b/man2/clock_getres.2
@@ -272,7 +272,7 @@ does not refer to a valid instance of a clock object.
.I tp.tv_sec
is negative or
.I tp.tv_nsec
-is outside the range [0..999,999,999].
+is outside the range [0, 999,999,999].
.TP
.B EINVAL
The
diff --git a/man2/clock_nanosleep.2 b/man2/clock_nanosleep.2
index 5afc2025c..5da8d1569 100644
--- a/man2/clock_nanosleep.2
+++ b/man2/clock_nanosleep.2
@@ -158,7 +158,7 @@ The sleep was interrupted by a signal handler; see
.B EINVAL
The value in the
.I tv_nsec
-field was not in the range 0 to 999999999 or
+field was not in the range [0, 999999999] or
.I tv_sec
was negative.
.TP
diff --git a/man2/getitimer.2 b/man2/getitimer.2
index f3fe06fb9..f092a2fc4 100644
--- a/man2/getitimer.2
+++ b/man2/getitimer.2
@@ -158,7 +158,7 @@ or (since Linux 2.6.22) one of the
.I tv_usec
fields in the structure pointed to by
.I new_value
-contains a value outside the range 0 to 999999.
+contains a value outside the range [0, 999999].
.SH STANDARDS
POSIX.1-2001, SVr4, 4.4BSD (this call first appeared in 4.2BSD).
POSIX.1-2008 marks
@@ -253,7 +253,7 @@ POSIX.1-2001 says that
.BR setitimer ()
should fail if a
.I tv_usec
-value is specified that is outside of the range 0 to 999999.
+value is specified that is outside of the range [0, 999999].
However, up to and including Linux 2.6.21,
Linux does not give an error, but instead silently
adjusts the corresponding seconds value for the timer.
diff --git a/man2/gettimeofday.2 b/man2/gettimeofday.2
index 9fe7a415d..d7f1dbe2b 100644
--- a/man2/gettimeofday.2
+++ b/man2/gettimeofday.2
@@ -152,7 +152,7 @@ is invalid.
.I tv.tv_sec
is negative or
.I tv.tv_usec
-is outside the range [0..999,999].
+is outside the range [0, 999,999].
.TP
.BR EINVAL " (since Linux 4.3)"
.\" commit e1d7ba8735551ed79c7a0463a042353574b96da3
diff --git a/man2/nanosleep.2 b/man2/nanosleep.2
index a6f9e627f..12e0cee84 100644
--- a/man2/nanosleep.2
+++ b/man2/nanosleep.2
@@ -66,7 +66,7 @@ The
structure
is used to specify intervals of time with nanosecond precision.
.PP
-The value of the nanoseconds field must be in the range 0 to 999999999.
+The value of the nanoseconds field must be in the range [0, 999999999].
.PP
Compared to
.BR sleep (3)
@@ -106,7 +106,7 @@ again and continue with the pause.
.B EINVAL
The value in the
.I tv_nsec
-field was not in the range 0 to 999999999 or
+field was not in the range [0, 999999999] or
.I tv_sec
was negative.
.SH STANDARDS
diff --git a/man2/utimensat.2 b/man2/utimensat.2
index 0ea9ebe9e..c2e6a9164 100644
--- a/man2/utimensat.2
+++ b/man2/utimensat.2
@@ -272,7 +272,7 @@ Invalid value in
.B EINVAL
Invalid value in one of the
.I tv_nsec
-fields (value outside range 0 to 999,999,999, and not
+fields (value outside range [0, 999,999,999], and not
.B UTIME_NOW
or
.BR UTIME_OMIT );