From 98895092a0a810773d3e9f9ab0807048c064e4fe Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Tue, 13 Jan 2009 02:12:09 +1300 Subject: [PATCH] signalfd.2: Fix description of fork() semantics The page text described the semantics of the initial implementation of signalfd(). These were changed early on, but the man page wasn't updated. Reported-by: Vegard Nossum Reviewed-by: Davide Libenzi Signed-off-by: Michael Kerrisk --- man2/signalfd.2 | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/man2/signalfd.2 b/man2/signalfd.2 index 188426c97..ea594ae18 100644 --- a/man2/signalfd.2 +++ b/man2/signalfd.2 @@ -16,7 +16,7 @@ .\" Foundation, Inc., 59 Temple Place, Suite 330, Boston, .\" MA 02111-1307 USA .\" -.TH SIGNALFD 2 2008-10-20 Linux "Linux Programmer's Manual" +.TH SIGNALFD 2 2009-01-13 Linux "Linux Programmer's Manual" .SH NAME signalfd \- create a file descriptor for accepting signals .SH SYNOPSIS @@ -219,14 +219,10 @@ for details. After a .BR fork (2), the child inherits a copy of the signalfd file descriptor. -The file descriptor refers to the same underlying -file object as the corresponding descriptor in the parent, -and -.BR read (2)s -in the child will return information about signals generated -for the parent -(the process that created the object using -.BR signalfd ()). +A +.BR read (2) +from the file descriptor in the child will return information +about signals queued to the child. .SS execve(2) semantics Just like any other file descriptor, a signalfd file descriptor remains open across an