Added SEE ALSO referring to new time.7

man2/getitimer.2

@@ -132,7 +132,8 @@ POSIX.1-2001, SVr4, 4.4BSD (this call first appeared in 4.2BSD).
 .SH "SEE ALSO"
 .BR gettimeofday (2),
 .BR sigaction (2),
-.BR signal (2)
+.BR signal (2),
+.BR time (7)
 .SH BUGS
 The generation and delivery of a signal are distinct, and
 only one instance of each of the signals listed above may be pending

man2/gettimeofday.2

@@ -234,4 +234,5 @@ but not
 .BR time (2),
 .BR ctime (3),
 .BR ftime (3),
-.BR capabilities (7)
+.BR capabilities (7),
+.BR time (7)

man2/nanosleep.2

@@ -106,7 +106,8 @@ was negative.
 The current implementation of
 .BR nanosleep ()
 is based on the normal kernel timer mechanism, which has a resolution
-of 1/\fIHZ\fR\ s (i.e, 10\ ms on Linux/i386 and 1\ ms on Linux/Alpha).
+of 1/\fIHZ\fR\ s (see
+.BR time (7)).
 Therefore,
 .BR nanosleep ()
 pauses always for at least the specified time, however it can take up
@@ -114,7 +115,6 @@ to 10 ms longer than specified until the process becomes runnable
 again. For the same reason, the value returned in case of a delivered
 signal in *\fIrem\fR is usually rounded to the next larger multiple of
 1/\fIHZ\fR\ s.
-
 .SS "Old behaviour"
 In order to support applications requiring much more precise pauses
 (e.g., in order to control some time-critical hardware),

man2/time.2

@@ -73,4 +73,5 @@ POSIX does not specify any error conditions.
 .BR date (1),
 .BR gettimeofday (2),
 .BR ctime (3),
-.BR ftime (3)
+.BR ftime (3),
+.BR time (7)

man2/times.2

@@ -173,4 +173,5 @@ by the variable HZ.
 .BR getrusage (2),
 .BR wait (2),
 .BR clock (3),
-.BR sysconf (3)
+.BR sysconf (3),
+.BR time (7)

man3/ctime.3

@@ -230,4 +230,5 @@ SVID 3, POSIX, 4.3BSD, ISO 9899
 .BR difftime (3),
 .BR strftime (3),
 .BR strptime (3),
-.BR tzset (3)
+.BR tzset (3),
+.BR time (7)

man4/rtc.4

@@ -221,4 +221,5 @@ and 2069.
 .BR settimeofday (2),
 .BR adjtimex (2),
 .BR gmtime (3),
+.BR time (7),
 /usr/src/linux/Documentation/rtc.txt