#timeout #wait #windows #unix #process #child

bin+lib wait-timeout

A crate to wait on a child process with a timeout specified across Unix and Windows platforms

7 releases

0.2.0 Nov 23, 2018
0.1.5 Mar 7, 2017
0.1.4 Feb 10, 2017
0.1.3 Feb 21, 2016
0.1.0 Sep 8, 2015

#12 in Operating systems

Download history 10182/week @ 2019-01-23 11267/week @ 2019-01-30 13503/week @ 2019-02-06 11553/week @ 2019-02-13 12260/week @ 2019-02-20 11855/week @ 2019-02-27 12812/week @ 2019-03-06 12581/week @ 2019-03-13 10687/week @ 2019-03-20 12863/week @ 2019-03-27 14347/week @ 2019-04-03 15659/week @ 2019-04-10 12924/week @ 2019-04-17 14046/week @ 2019-04-24 13118/week @ 2019-05-01

36,102 downloads per month
Used in 18 crates (16 directly)

MIT/Apache

17KB
263 lines

wait-timeout

Build Status Build status

Documentation

Rust crate for waiting on a Child process with a timeout specified.

# Cargo.toml
[dependencies]
wait-timeout = "0.1.5"

lib.rs:

A crate to wait on a child process with a particular timeout.

This crate is an implementation for Unix and Windows of the ability to wait on a child process with a timeout specified. On Windows the implementation is fairly trivial as it's just a call to WaitForSingleObject with a timeout argument, but on Unix the implementation is much more involved. The current implementation registers a SIGCHLD handler and initializes some global state. This handler also works within multi-threaded environments. If your application is otherwise handling SIGCHLD then bugs may arise.

Example

use std::process::Command;
use wait_timeout::ChildExt;
use std::time::Duration;

let mut child = Command::new("foo").spawn().unwrap();

let one_sec = Duration::from_secs(1);
let status_code = match child.wait_timeout(one_sec).unwrap() {
    Some(status) => status.code(),
    None => {
        // child hasn't exited yet
        child.kill().unwrap();
        child.wait().unwrap().code()
    }
};

Dependencies

~49KB