I'm trying to write some code that will catch a signal like SIGTERM.
I found this and I also found How to handle blocking i/o in Rust, or long running external function calls in general.
But in the current Rust version (0.12 nightly) it seems like that std::io::signal::Listener
was removed. Did it get put somewhere else? If so can someone point me to how to catch a signal?
It seems that it's now fairly trivial to implement this. The Signal handling section of Command Line Applications in Rust goes over the concept, and mentions the ctrlc crate to handle that specific signal, and the signal-hook crate to handle signals in general.
Via the guide, with signal-hook it should be as simple as:
use std::{error::Error, thread}; use signal_hook::{iterator::Signals, SIGTERM}; fn main() -> Result<(), Box<Error>> { let signals = Signals::new(&[SIGTERM])?; thread::spawn(move || { for sig in signals.forever() { println!("Received signal {:?}", sig); } }); Ok(()) }
I believe that std::io::signal
module was removed in this pull request. It is claimed that proper signals handling was never implemented properly for native runtime, so you likely wouldn't be able to use it now anyway. This seems to be a tracking issue for this problem.
In the meantime, I think, you will have to drop down to the lowest-level unsafe functions from libc
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With