Thread (10 messages) 10 messages, 2 authors, 2024-07-09

Re: [PATCH] sigaction.2: setitimer(2)/alarm(2) timers yield si_code=SI_TIMER too

From: Alejandro Colomar <alx@kernel.org>
Date: 2024-07-09 16:38:45

Hi наб,

On Mon, Jul 08, 2024 at 04:03:40AM GMT, наб wrote:
Applies to Linux and NetBSD.
Is this non-standard behavior?  Should we mention something about it?

Cheers,
Alex
quoted hunk ↗ jump to hunk
Signed-off-by: Ahelenia Ziemiańska <redacted>
---
 man/man2/sigaction.2 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/man/man2/sigaction.2 b/man/man2/sigaction.2
index ce5ad7579..538028f54 100644
--- a/man/man2/sigaction.2
+++ b/man/man2/sigaction.2
@@ -645,7 +645,9 @@ .SS The si_code field
 .BR sigqueue (3).
 .TP
 .B SI_TIMER
-POSIX timer expired.
+POSIX or
+.BR setitimer (2)/ alarm (2)
+timer expired.
 .TP
 .BR SI_MESGQ " (since Linux 2.6.6)"
 POSIX message queue state changed; see
-- 
2.39.2


-- 
<https://www.alejandro-colomar.es/>

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help