#child-process #unix-windows #timeout #windows-platform #waiting

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

#5 in #unix-windows

Download history 470005/week @ 2026-03-03 2790271/week @ 2026-03-10 2451036/week @ 2026-03-17 2394279/week @ 2026-03-24 2471588/week @ 2026-03-31 2680674/week @ 2026-04-07 2753159/week @ 2026-04-14 2981296/week @ 2026-04-21 3018652/week @ 2026-04-28 3189987/week @ 2026-05-05 3753716/week @ 2026-05-12 3664554/week @ 2026-05-19 3733143/week @ 2026-05-26 3403446/week @ 2026-06-02

15,092,007 downloads per month
Used in 4,652 crates (192 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

~42KB