|
Check-in Number:
|
138 | |
| Date: |
2000-Aug-17 10:47:51 (local)
2000-Aug-17 08:47:51 (UTC) |
| User: | rse |
| Branch: | |
| Comment: |
*** empty log message *** |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/pth/ChangeLog 1.527 -> 1.528
--- ChangeLog 2000/08/18 08:35:29 1.527
+++ ChangeLog 2000/08/18 08:47:51 1.528
@@ -25,10 +25,6 @@
if an argument of zero is given.
[Ralf S. Engelschall]
- *) Added description of return code semantics for pth_sleep(3)
- and pth_usleep(3) to pth.pod.
- [Ralf S. Engelschall]
-
*) Fixed pthread.pod: the newer pod2man versions seems to dislike
embedded comments, so I moved them to the top of the file.
[Ralf S. Engelschall]
|
|
ossp-pkg/pth/pth.3 1.222 -> 1.223
--- 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
|
|
ossp-pkg/pth/pth.pod 1.140 -> 1.141
--- pth.pod 2000/08/18 08:35:29 1.140
+++ pth.pod 2000/08/18 08:47:51 1.141
@@ -1584,26 +1584,20 @@
This is a variant of the 4.3BSD usleep(3) function. It suspends the current
threads execution until I<usec> microseconds (= I<usec>*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 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 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.
+the whole process.
=item unsigned int B<pth_sleep>(unsigned int I<sec>);
-This is a variant of the POSIX sleep(3) function. It
-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
-pth_sleep(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 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.
+This is a variant of the POSIX sleep(3) function. It 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 pth_sleep(3) suspends only the
+execution of the current thread and not the whole process.
=item pid_t B<pth_waitpid>(pid_t I<pid>, int *I<status>, int I<options>);
|
|
