From 54d02f32e947ea1ebb0312c24c12d31561a363f9 Mon Sep 17 00:00:00 2001
From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Fri, 29 Feb 2008 16:28:54 +0000
Subject: [PATCH] Further reworking of Q5/A5.

---
 man7/epoll.7 | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/man7/epoll.7 b/man7/epoll.7
index 24e3a2aaf..1db7d193b 100644
--- a/man7/epoll.7
+++ b/man7/epoll.7
@@ -172,8 +172,9 @@ In this example, listener is a
 non-blocking socket on which
 .BR listen (2)
 has been called.
-The function do_use_fd() uses the new ready
-file descriptor until
+The function
+.I do_use_fd()
+uses the new ready file descriptor until
 .B EAGAIN
 is returned by either
 .BR read (2)
@@ -181,7 +182,8 @@ or
 .BR write (2).
 An event-driven state machine application should, after having received
 .BR EAGAIN ,
-record its current state so that at the next call to do_use_fd()
+record its current state so that at the next call to
+.I do_use_fd()
 it will continue to
 .BR read (2)
 or
@@ -327,12 +329,15 @@ file descriptor inside another
 file descriptor set.
 .TP
 .B Q5
-Can I send the
+Can I send an
 .B epoll
 file descriptor over a Unix domain socket to another process?
 .TP
 .B A5
-No.
+Yes, but it does not make sense to do this, since the receiving process
+would not have copies of the file descriptors in the
+.B epoll
+set.
 .TP
 .B Q6
 Will closing a file descriptor cause it to be removed from all