--- pth.pod 2000/09/30 08:00:18 1.142
+++ pth.pod 2000/10/03 09:26:47 1.143
@@ -159,6 +159,7 @@
pth_usleep,
pth_sleep,
pth_waitpid,
+pth_system,
pth_sigmask,
pth_sigwait,
pth_accept,
@@ -1608,6 +1609,15 @@
current thread and not the whole process. For more details about the
arguments and return code semantics see waitpid(2).
+=item int B<pth_system>(const char *I<cmd>);
+
+This is a variant of the POSIX system(3) function. It executes the
+shell command I<cmd> with Bourne Shell (C<sh>) and suspends the current
+threads execution until this command terminates. The difference between
+system(3) and pth_system(3) is that that pth_system(3) suspends only
+the execution of the current thread and not the whole process. For more
+details about the arguments and return code semantics see system(3).
+
=item int B<pth_sigmask>(int I<how>, const sigset_t *I<set>, sigset_t *I<oset>)
This is the B<Pth> thread-related equivalent of POSIX sigprocmask(2) respectively
@@ -2128,8 +2138,8 @@
building B<Pth> with C<--enable-syscall-soft>. This then triggers some
C<#define>'s in the C<pth.h> header which map for instance read(3) to
pth_read(3), etc. Currently the following functions are mapped: fork(2),
-sleep(3), sigwait(3), waitpid(2), select(2), poll(2), connect(2),
-accept(2), read(2), write(2).
+sleep(3), sigwait(3), waitpid(2), system(3), select(2), poll(2),
+connect(2), accept(2), read(2), write(2).
The drawback of this approach is just that really all source files
of the application where these function calls occur have to include
@@ -2143,9 +2153,9 @@
function exists and there it can be enabled by building B<Pth> with
C<--enable-syscall-hard>. This then builds wrapper functions (for instances
read(3)) into the B<Pth> library which internally call the real B<Pth>
-replacement functions (pth_read(3)). Currently the following functions are
-mapped: fork(2), sleep(3), waitpid(2), select(2), poll(2), connect(2),
-accept(2), read(2), write(2).
+replacement functions (pth_read(3)). Currently the following functions
+are mapped: fork(2), sleep(3), waitpid(2), system(3), select(2),
+poll(2), connect(2), accept(2), read(2), write(2).
The drawback of this approach is that it depends on syscall(2) interface
and prototype conflicts can occur while building the wrapper functions
|
