Ivan Petkov d8b23ef852 signal: rename SignalKind methods (#1457)
This renames the SignalKind constructors to be a bit more readable
instead of using the signal names themselves
2019-08-15 21:09:09 -07:00

48 lines
1.4 KiB
Rust

#![warn(rust_2018_idioms)]
#![feature(async_await)]
//! A small example of how to listen for two signals at the same time
// A trick to not fail build on non-unix platforms when using unix-specific features.
#[cfg(unix)]
mod platform {
use futures_util::stream::{self, StreamExt};
use tokio_signal::unix::{Signal, SignalKind};
pub async fn main() {
// Create a stream for each of the signals we'd like to handle.
let sigint = Signal::new(SignalKind::interrupt())
.unwrap()
.map(|_| "SIGINT");
let sigterm = Signal::new(SignalKind::terminate())
.unwrap()
.map(|_| "SIGTERM");
// Use the `select` combinator to merge these two streams into one
let stream = stream::select(sigint, sigterm);
// Wait for a signal to arrive
println!("Waiting for SIGINT or SIGTERM");
println!(
" TIP: use `pkill -sigint multiple` from a second terminal \
to send a SIGINT to all processes named 'multiple' \
(i.e. this binary)"
);
let (item, _rest) = stream.into_future().await;
// Figure out which signal we received
let msg = item.ok_or("received no signal").unwrap();
println!("received {}", msg);
}
}
#[cfg(not(unix))]
mod platform {
pub async fn main() {}
}
#[tokio::main]
async fn main() {
platform::main().await
}