docs.rs failed to build mio-child-process-0.1.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
mio-child-process-0.2.1
A simple crate that allows child processes to be handled with mio
usage
extern crate mio_child_process;
extern crate mio;
use ;
use ;
use ;
use TryRecvError;
Notes
StdioChannel::Stdout will only be emitted when .stdout(Stdio::piped())
is passed to the Command
.
StdioChannel::Stderr will only be emitted when .stderr(Stdio::piped())
is passed to the Command
.
Threads
Internally a thread gets spawned for each std stream it's listening to (stdout and stderr). Another thread is started, that is in a blocking wait until the child process is done. This means that mio-child-process uses between 1 to 3 threads for every process that gets started.