linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walter harms <wharms-fPG8STNUNVg@public.gmane.org>
To: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Fwd: Re: syslog(3) inconsistency
Date: Fri, 24 Mar 2017 18:00:37 +0100	[thread overview]
Message-ID: <58D550B5.4020105@bfs.de> (raw)





Am 24.03.2017 15:40, schrieb Michael Kerrisk (man-pages):
> Hello Ian,
> 
> On 03/23/2017 07:37 PM, Ian Abbott wrote:
>> Hi,
>>
>> The first parameter of `syslog()` is called `priority` in the man-page, 
>> except in the breakdown of the possible log levels, where it is called 
>> `level`.
> 
> Your report doesn't say clearly which pieces of text you find to
> be incorrect, but I wonder if you have missed this sentence in the 
> man page:
> 
>     The priority argument is formed by ORing the facility and the
>     level values (explained below). 
> 
> If you still think there's a problem in the man page, could you please
> describe the problem in more detail.
>


I thing i have an idea what he is talking about. One option
os simply repeating the priority=(facility|level) sentence
as below. Otherwise a simple example would also be helpful.

re,
 wh

--- syslog.3.org	2017-03-24 15:58:02.000000000 +0100
+++ syslog.3	2017-03-24 15:57:10.000000000 +0100
@@ -167,6 +167,15 @@
 .TP
 .B LOG_PID
 Include PID with each message.
+
+.in 3
+The
+.B priority
+argument is formed by ORing the
+.I facility
+and the
+.I level
+values (explained below).
 .SS facility
 The
 .I facility



--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

                 reply	other threads:[~2017-03-24 17:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58D550B5.4020105@bfs.de \
    --to=wharms-fpg8stnunvg@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).