summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Lacroix <toto.rigolo@free.fr>2019-07-07 18:49:20 +0200
committerIvan Petkov <ivanppetkov@gmail.com>2019-07-07 09:49:19 -0700
commite07a03b3c5f7453f4360e0c72c805e6f5faaf32a (patch)
tree0a3d2f77d38e2cf606847f545f33ec71d6a498be
parent7b86acb71d11664f64104854ea69d41d9772786e (diff)
signal: update instructions in Ctrl-C example (#1270)
Fixes: #1248
-rw-r--r--tokio-signal/examples/ctrl-c.rs9
1 files changed, 3 insertions, 6 deletions
diff --git a/tokio-signal/examples/ctrl-c.rs b/tokio-signal/examples/ctrl-c.rs
index b3032b97..53f92744 100644
--- a/tokio-signal/examples/ctrl-c.rs
+++ b/tokio-signal/examples/ctrl-c.rs
@@ -22,12 +22,9 @@ async fn main() -> Result<(), Box<dyn std::error::Error>> {
let mut counter = 0;
println!(
- "This program is now waiting for you to press Ctrl+C {0} times.
- * If running via `cargo run --example ctrl-c`, Ctrl+C also kills it, \
- due to https://github.com/rust-lang-nursery/rustup.rs/issues/806
- * If running the binary directly, the Ctrl+C is properly trapped.
- Terminate by repeating Ctrl+C {0} times, or ahead of time by \
- opening a second terminal and issuing `pkill -sigkil ctrl-c`",
+ "This program is now waiting for you to press Ctrl+C {0} times. \
+ Terminate by repeating Ctrl+C {0} times, or ahead of time by opening \
+ a second terminal and issuing `pkill -sigkil ctrl-c`.",
STOP_AFTER
);