mirror of
https://github.com/tokio-rs/tokio.git
synced 2026-08-08 00:00:22 +02:00
Ivan PetkovandCarl Lerche
b6ecfa251c
* Currently, whenever a new signal stream is created we attempt to register a global pipe with the event loop to drive events. * We also (correctly) swallow any descriptor-already-registered errors since the same pipe is always used * However, we currently *deregister* the same global pipe *any time* a Signal stream is dropped. * This means that if 2 or more of Signal instances exist simultaneously (even if listening for different signals) and one of them is dropped, the remainder will starve (until any new signal is created again).
tokio-signal
An implementation of Unix signal handling for Tokio
Usage
First, add this to your Cargo.toml:
[dependencies]
tokio-signal = "0.1"
Next you can use this in conjunction with the tokio and futures crates:
extern crate futures;
extern crate tokio;
extern crate tokio_signal;
use futures::{Future, Stream};
fn main() {
// Create an infinite stream of "Ctrl+C" notifications. Each item received
// on this stream may represent multiple ctrl-c signals.
let ctrl_c = tokio_signal::ctrl_c().flatten_stream();
// Process each ctrl-c as it comes in
let prog = ctrl_c.for_each(|()| {
println!("ctrl-c received!");
Ok(())
});
tokio::run(prog.map_err(|err| panic!("{}", err)));
}
License
This project is licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in tokio-signal by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.