From 52cf88e2ef809b7b640e5dc0f8a4a92cee7461ec Mon Sep 17 00:00:00 2001 From: David Xu Date: Mon, 5 Dec 2005 09:31:49 +0000 Subject: [PATCH] Fix markup. Submitted by: ru --- lib/libc/sys/mq_notify.2 | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/lib/libc/sys/mq_notify.2 b/lib/libc/sys/mq_notify.2 index 53f55a92d7c..86a43631c97 100644 --- a/lib/libc/sys/mq_notify.2 +++ b/lib/libc/sys/mq_notify.2 @@ -61,15 +61,23 @@ The argument points to a .Vt sigevent structure that defines how the calling process will be notified. -If notification->sigev_notify is +If +.Fa notification->sigev_notify +is .Dv SIGEV_NONE , then no signal will be posted, but the error status and the return status for the operation will be set appropriately. -If notification->sigev_notify is SIGEV_SIGNAL, then the signal specified -in notification->sigev_signo will be sent to the process. +If +.Fa notification->sigev_notify +is +.Dv SIGEV_SIGNAL , +then the signal specified in +.Fa notification->sigev_signo +will be sent to the process. The signal will be queued to the process and the value specified in -notification->sigev_value will be the si_value component of the generated -signal. +notification->sigev_value will be the +.Va si_value +component of the generated signal. .Pp If .Fa notification