#command

bin+lib wait-timeout

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

7 releases

Uses old Rust 2015

0.2.1 Feb 3, 2025
0.2.0 Nov 23, 2018
0.1.5 Mar 7, 2017
0.1.4 Feb 10, 2017
0.1.0 Sep 8, 2015

#12 in Operating systems

Download history 594833/week @ 2024-12-05 656024/week @ 2024-12-12 387747/week @ 2024-12-19 290499/week @ 2024-12-26 596570/week @ 2025-01-02 806836/week @ 2025-01-09 729386/week @ 2025-01-16 812025/week @ 2025-01-23 876889/week @ 2025-01-30 1019136/week @ 2025-02-06 959370/week @ 2025-02-13 1037259/week @ 2025-02-20 1137139/week @ 2025-02-27 1435842/week @ 2025-03-06 1349542/week @ 2025-03-13 1667024/week @ 2025-03-20

5,782,929 downloads per month
Used in 1,736 crates (78 directly)

MIT/Apache

17KB
242 lines

wait-timeout

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

~44KB