--- pth.3 2000/10/03 08:00:35 1.225
+++ pth.3 2001/02/25 17:15:54 1.226
@@ -1,5 +1,5 @@
.\" Automatically generated by Pod::Man version 1.02
-.\" Sun Oct 1 14:44:33 2000
+.\" Sun Feb 25 18:13:54 2001
.\"
.\" Standard preamble:
.\" ======================================================================
@@ -253,6 +253,7 @@
pth_usleep,
pth_sleep,
pth_waitpid,
+pth_system,
pth_sigmask,
pth_sigwait,
pth_accept,
@@ -1501,6 +1502,14 @@
\&\fIpth_waitpid\fR\|(3) is that that \fIpth_waitpid\fR\|(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 \fIwaitpid\fR\|(2).
+.Ip "int \fBpth_system\fR(const char *\fIcmd\fR);" 4
+.IX Item "int pth_system(const char *cmd);"
+This is a variant of the \s-1POSIX\s0 \fIsystem\fR\|(3) function. It executes the
+shell command \fIcmd\fR with Bourne Shell (\f(CW\*(C`sh\*(C'\fR) and suspends the current
+threads execution until this command terminates. The difference between
+\&\fIsystem\fR\|(3) and \fIpth_system\fR\|(3) is that that \fIpth_system\fR\|(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 \fIsystem\fR\|(3).
.Ip "int \fBpth_sigmask\fR(int \fIhow\fR, const sigset_t *\fIset\fR, sigset_t *\fIoset\fR)" 4
.IX Item "int pth_sigmask(int how, const sigset_t *set, sigset_t *oset)"
This is the \fBPth\fR thread-related equivalent of \s-1POSIX\s0 \fIsigprocmask\fR\|(2) respectively
@@ -2022,8 +2031,8 @@
building \fBPth\fR with \f(CW\*(C`\-\-enable\-syscall\-soft\*(C'\fR. This then triggers some
\&\f(CW\*(C`#define\*(C'\fR's in the \f(CW\*(C`pth.h\*(C'\fR header which map for instance \fIread\fR\|(3) to
\&\fIpth_read\fR\|(3), etc. Currently the following functions are mapped: \fIfork\fR\|(2),
-\&\fIsleep\fR\|(3), \fIsigwait\fR\|(3), \fIwaitpid\fR\|(2), \fIselect\fR\|(2), \fIpoll\fR\|(2), \fIconnect\fR\|(2),
-\&\fIaccept\fR\|(2), \fIread\fR\|(2), \fIwrite\fR\|(2).
+\&\fIsleep\fR\|(3), \fIsigwait\fR\|(3), \fIwaitpid\fR\|(2), \fIsystem\fR\|(3), \fIselect\fR\|(2), \fIpoll\fR\|(2),
+\&\fIconnect\fR\|(2), \fIaccept\fR\|(2), \fIread\fR\|(2), \fIwrite\fR\|(2).
.PP
The drawback of this approach is just that really all source files
of the application where these function calls occur have to include
@@ -2036,9 +2045,9 @@
function exists and there it can be enabled by building \fBPth\fR with
\&\f(CW\*(C`\-\-enable\-syscall\-hard\*(C'\fR. This then builds wrapper functions (for instances
\&\fIread\fR\|(3)) into the \fBPth\fR library which internally call the real \fBPth\fR
-replacement functions (\fIpth_read\fR\|(3)). Currently the following functions are
-mapped: \fIfork\fR\|(2), \fIsleep\fR\|(3), \fIwaitpid\fR\|(2), \fIselect\fR\|(2), \fIpoll\fR\|(2), \fIconnect\fR\|(2),
-\&\fIaccept\fR\|(2), \fIread\fR\|(2), \fIwrite\fR\|(2).
+replacement functions (\fIpth_read\fR\|(3)). Currently the following functions
+are mapped: \fIfork\fR\|(2), \fIsleep\fR\|(3), \fIwaitpid\fR\|(2), \fIsystem\fR\|(3), \fIselect\fR\|(2),
+\&\fIpoll\fR\|(2), \fIconnect\fR\|(2), \fIaccept\fR\|(2), \fIread\fR\|(2), \fIwrite\fR\|(2).
.PP
The drawback of this approach is that it depends on \fIsyscall\fR\|(2) interface
and prototype conflicts can occur while building the wrapper functions
|
