--- pth.pod 2000/08/01 06:13:15 1.139
+++ pth.pod 2000/08/18 08:35:29 1.140
@@ -1583,12 +1583,14 @@
=item int B<pth_usleep>(unsigned int I<usec>);
This is a variant of the 4.3BSD usleep(3) function. It suspends the current
-threads execution until I<usec> microsecond (= I<usec> * 1/1000000 sec)
-elapsed. The thread is guaranteed to not awakened before this time, but
+threads execution until I<usec> microseconds (= I<usec>*1/1000000 sec)
+elapsed. The thread is guaranteed to not awakened before this time, but
because of the non-preemptive scheduling nature of B<Pth>, it can be awakened
-later, of course. The difference between usleep(3) and pth_usleep(3) is that
+later, of course. The difference between usleep(3) and pth_usleep(3) is that
that pth_usleep(3) suspends only the execution of the current thread and not
-the whole process.
+the whole process. The function returns the value C<0> if successful,
+otherwise the value C<-1> is returned and the global variable C<errno> is set
+to indicate the error.
=item unsigned int B<pth_sleep>(unsigned int I<sec>);
@@ -1596,9 +1598,12 @@
suspends the current threads execution until I<sec> seconds elapsed. The
thread is guaranteed to not awakened before this time, but because of the
non-preemptive scheduling nature of B<Pth>, it can be awakened later, of
-course. The difference between sleep(3) and pth_sleep(3) is that that
+course. The difference between sleep(3) and pth_sleep(3) is that that
pth_sleep(3) suspends only the execution of the current thread and not the
-whole process.
+whole process. If the function returns because the requested time has
+elapsed, the value returned will be C<0>. 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.
=item pid_t B<pth_waitpid>(pid_t I<pid>, int *I<status>, int I<options>);
|
