#child-process #timeout #wait #waiting #handler #unix #sigchld

bin+lib wait-timeout

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

6 releases

Uses old Rust 2015

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

#63 in Operating systems

Download history 152234/week @ 2023-12-23 256595/week @ 2023-12-30 301904/week @ 2024-01-06 313946/week @ 2024-01-13 328420/week @ 2024-01-20 317927/week @ 2024-01-27 308714/week @ 2024-02-03 296680/week @ 2024-02-10 310566/week @ 2024-02-17 326241/week @ 2024-02-24 346972/week @ 2024-03-02 332743/week @ 2024-03-09 342799/week @ 2024-03-16 339233/week @ 2024-03-23 344008/week @ 2024-03-30 286992/week @ 2024-04-06

1,365,065 downloads per month
Used in 1,365 crates (62 directly)

MIT/Apache

18KB
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

~42KB