create_process cmd f
runs cmd and hands details of the process to f. When f is
determined, or when f throws an exception, the background process is killed gracefully
(TERM, wait, then KILL), all file descriptors are closed, and the process is reaped
create_fds...
like create, except that the three file_descrs to be used for the
stdin/stdout/stderr of the forked process are passed in. The passed-in file_descrs
might for example have been obtained by a called to Unix.pipe().
create_fds'...
like create_fds
except that we wait for caller's f
to become
determined before calling Unix.waitpid
. Also, result of caller's f
is return with
Exit_or_signal.t
open_in ~prog ~args
runs prog with args and returns a readers connected to stdout
and stderr. When both of those readers are closed then the process is reaped (and
killed if necessary). is_ok defaults to Core.Std.Unix.Exit_or_signal.ok.
backtick_status ~prog ~args
runs prog with args and returns the full
stdout and stderr as strings, together with the process status. If
stdin
is provided, it will be written to the stdin of the program, but
no guarantees are made as to whether the program actually reads this
data. In particular, the program may close stdin, or exit before the
data has been read; no error is raised in these circumstances. This
behaviour is akin to:
echo stdin | ...
at the shell prompt.
backtick ~prog ~args
runs prog with args and returns the full stdout and stderr
as strings (ignoring the process status)