#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

#62 in Operating systems

Download history 337441/week @ 2024-03-14 349557/week @ 2024-03-21 330126/week @ 2024-03-28 343168/week @ 2024-04-04 353778/week @ 2024-04-11 345615/week @ 2024-04-18 342262/week @ 2024-04-25 352942/week @ 2024-05-02 346612/week @ 2024-05-09 375826/week @ 2024-05-16 368224/week @ 2024-05-23 398644/week @ 2024-05-30 375496/week @ 2024-06-06 388913/week @ 2024-06-13 372669/week @ 2024-06-20 329018/week @ 2024-06-27

1,543,855 downloads per month
Used in 1,430 crates (65 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

~43KB