--- pth.3 2000/08/18 08:35:29 1.222
+++ pth.3 2000/08/18 08:47:51 1.223
@@ -1369,24 +1369,18 @@
.Ip "int \fBpth_usleep\fR(unsigned int \fIusec\fR);" 4
This is a variant of the 4.3BSD \fIusleep\fR\|(3) function. It suspends the current
threads execution until \fIusec\fR microseconds (= \fIusec\fR*1/1000000 sec)
-elapsed. The thread is guaranteed to not awakened before this time, but
+elapsed. The thread is guaranteed to not awakened before this time, but
because of the non-preemptive scheduling nature of \fBPth\fR, it can be awakened
-later, of course. The difference between \fIusleep\fR\|(3) and \fIpth_usleep\fR\|(3) is that
+later, of course. The difference between \fIusleep\fR\|(3) and \fIpth_usleep\fR\|(3) is that
that \fIpth_usleep\fR\|(3) suspends only the execution of the current thread and not
-the whole process. The function returns the value \f(CW0\fR if successful,
-otherwise the value \f(CW-1\fR is returned and the global variable \f(CWerrno\fR is set
-to indicate the error.
+the whole process.
.Ip "unsigned int \fBpth_sleep\fR(unsigned int \fIsec\fR);" 4
-This is a variant of the \s-1POSIX\s0 \fIsleep\fR\|(3) function. It
-suspends the current threads execution until \fIsec\fR seconds elapsed. The
-thread is guaranteed to not awakened before this time, but because of the
-non-preemptive scheduling nature of \fBPth\fR, it can be awakened later, of
-course. The difference between \fIsleep\fR\|(3) and \fIpth_sleep\fR\|(3) is that that
-\fIpth_sleep\fR\|(3) suspends only the execution of the current thread and not the
-whole process. If the function returns because the requested time has
-elapsed, the value returned will be \f(CW0\fR. If the function returns due to the
-delivery of a signal, the value returned will be the unslept amount (the
-requested time minus the time actually slept) in seconds.
+This is a variant of the \s-1POSIX\s0 \fIsleep\fR\|(3) function. It suspends the current
+threads execution until \fIsec\fR seconds elapsed. The thread is guaranteed to
+not awakened before this time, but because of the non-preemptive scheduling
+nature of \fBPth\fR, it can be awakened later, of course. The difference between
+\fIsleep\fR\|(3) and \fIpth_sleep\fR\|(3) is that that \fIpth_sleep\fR\|(3) suspends only the
+execution of the current thread and not the whole process.
.Ip "pid_t \fBpth_waitpid\fR(pid_t \fIpid\fR, int *\fIstatus\fR, int \fIoptions\fR);" 4
This is a variant of the \s-1POSIX\s0 \fIwaitpid\fR\|(2) function. It suspends the
current threads execution until \fIstatus\fR information is available for a
|
