From 4d8ff2b1bbfd69c1831536026f9518b1fe0f6459 Mon Sep 17 00:00:00 2001 From: yellowhatter <104833606+yellowhatter@users.noreply.github.com> Date: Tue, 17 Sep 2024 11:20:24 +0300 Subject: [PATCH] [skip ci] doc comment update Co-authored-by: Luca Cominardi --- commons/zenoh-shm/src/api/cleanup.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/commons/zenoh-shm/src/api/cleanup.rs b/commons/zenoh-shm/src/api/cleanup.rs index db6de74046..9b2fa2c50f 100644 --- a/commons/zenoh-shm/src/api/cleanup.rs +++ b/commons/zenoh-shm/src/api/cleanup.rs @@ -17,7 +17,7 @@ use crate::cleanup::CLEANUP; /// Make forced cleanup /// NOTE: this is a part of a temporary on-exit-cleanup workaround and it will be very likely removed in the future. /// In order to properly cleanup some SHM internals upon process exit, Zenoh installs exit handlers (see atexit() API). -/// The bad thing is that atexit handler is executed only on process exit(), the terminating signal handlers (like SIGINT) +/// The atexit handler is executed only on process exit(), the inconvenience is that terminating signal handlers (like SIGINT) /// bypass it and terminate the process without cleanup. To eliminate this effect, Zenoh overrides SIGHUP, SIGTERM, SIGINT /// and SIGQUIT handlers and calls exit() inside to make graceful shutdown. If user is going to override these Zenoh's handlers, /// the workaround will break, and there are two ways to keep this workaround working: