Crates.io | ctrlc2 |
lib.rs | ctrlc2 |
version | 3.5.8 |
source | src |
created_at | 2023-11-05 06:35:34.588742 |
updated_at | 2024-08-27 02:49:36.372248 |
description | Easy Ctrl-C handler version 2 for Rust projects |
homepage | https://github.com/ssrlive/ctrlc2 |
repository | https://github.com/ssrlive/ctrlc2.git |
max_upload_size | |
id | 1025783 |
size | 58,758 |
For this reason, I have decided to create a fork of ctrlc and maintain it. I will try to keep it up to date with the original repo. If you have any suggestions or want to contribute, please open an issue or a PR. Thanks! I will respond to issues and PRs as soon as possible.
A simple easy to use wrapper around Ctrl-C signal.
In cargo.toml
:
[dependencies]
ctrlc2 = "3.5"
then, in main.rs
use std::sync::mpsc::channel;
use ctrlc2;
fn main() {
let (tx, rx) = channel();
let handle = ctrlc2::set_handler(move || {tx.send(()).expect("Could not send signal on channel."); true})
.expect("Error setting Ctrl-C handler");
println!("Waiting for Ctrl-C...");
rx.recv().expect("Could not receive from channel.");
println!("Got it! Exiting...");
handle.join().unwrap();
}
This library now supports asynchronous operation using either the tokio runtimes.
Selecting the tokio is done using feature flags (e.g. --no-default-features --features tokio)
#[cfg(feature = "tokio")]
#[cfg_attr(feature = "tokio", tokio::main(flavor = "current_thread"))]
async fn main() {
let (tx, mut rx) = tokio::sync::mpsc::channel::<()>(1);
ctrlc2::set_async_handler(async move {
tx.send(())
.await
.expect("Could not send signal on channel.");
})
.await;
println!("Waiting for Ctrl-C...");
rx.recv().await.expect("Could not receive from channel.");
println!("Got it! Exiting...");
}
cargo build --examples && target/debug/examples/readme_example
Add CtrlC to Cargo.toml using termination
feature and CtrlC will handle SIGINT, SIGTERM and SIGHUP.
Licensed under either of
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you shall be dual licensed as above, without any additional terms or conditions.
There are alternatives that give you more control over the different signals and/or add async support.