#child-process #timeout #wait #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

#20 in Operating systems

Download history 588302/week @ 2024-10-25 544084/week @ 2024-11-01 558373/week @ 2024-11-08 554102/week @ 2024-11-15 491530/week @ 2024-11-22 516127/week @ 2024-11-29 625778/week @ 2024-12-06 649845/week @ 2024-12-13 312606/week @ 2024-12-20 337727/week @ 2024-12-27 642870/week @ 2025-01-03 814114/week @ 2025-01-10 730868/week @ 2025-01-17 820487/week @ 2025-01-24 895556/week @ 2025-01-31 1041546/week @ 2025-02-07

3,637,774 downloads per month
Used in 1,677 crates (77 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

~43KB