public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Jeremy Kerr <jk-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
Cc: Michael Kerrisk
	<mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/3] syslog: document all type options
Date: Thu, 14 Feb 2008 19:54:06 +0100	[thread overview]
Message-ID: <47B48E4E.8080002@gmail.com> (raw)
In-Reply-To: <1202861911.426160.527338481577.qpush@pokey>

Thanks Jeremy.  Applied for man-pages-2.79.

One comment below.

Jeremy Kerr wrote:
> The type=6 and above options to syslog aren't documented, so
> add a sentence about each.
> 
> Signed-off-by: Jeremy Kerr <jk-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
> 
> ---
> 
>  man2/syslog.2 |   33 +++++++++++++++++++++++++++++++++
>  1 file changed, 33 insertions(+)
> 
> Index: man-pages-2.77/man2/syslog.2
> ===================================================================
> --- man-pages-2.77.orig/man2/syslog.2
> +++ man-pages-2.77/man2/syslog.2
> @@ -115,6 +115,39 @@ The call
>  .RI (5, dummy , idummy )
>  only executes the "clear ring buffer" command.
>  
> +The call
> +.BR syslog ()
> +.RI (6, dummy , dummy )

Here you are replicating a bad formatting glitch that I introduced a while
back when doing a semiautomated edit of this page a while back.

I reformatted these as simply

.I syslog(6,dummy,dummy)

etc.

Cheers,

Michael

> +sets the console log level to minimum, so that no messages are printed
> +to the console.
> +
> +The call
> +.BR syslog ()
> +.RI (7, dummy , dummy )
> +sets the console log level to default, so that messages are printed
> +to the console.
> +
> +The call
> +.BR syslog ()
> +.RI (8, dummy , level )
> +sets the console log level to
> +.IR level .
> +Which is an integer between 1 and 8 (inclusive).

I made that last piece:

The call
.I syslog(8,dummy,level)
sets the console log level to
.IR level ,
which must be an integer between 1 and 8 (inclusive).

> +See the
> +.B loglevel
> +section for details.
> +
> +The call
> +.BR syslog ()
> +.RI (9, dummy , dummy )
> +queries and returns the number of bytes currently available to be read
> +on the kernel log buffer.
> +
> +The call
> +.BR syslog ()
> +.RI (10, dummy , dummy )
> +queries and returns the total size of the kernel log buffer.
> +
>  .B The loglevel
>  .br
>  The kernel routine
> 

-- 
Michael Kerrisk
Maintainer of the Linux man-pages project
http://www.kernel.org/doc/man-pages/
Want to report a man-pages bug?  Look here:
http://www.kernel.org/doc/man-pages/reporting_bugs.html

  reply	other threads:[~2008-02-14 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  0:18 [PATCH 0/3] syslog.2 updates Jeremy Kerr
2008-02-13  0:18 ` [PATCH 2/3] syslog: printk isn't posessive, or a contraction Jeremy Kerr
2008-02-14 18:54   ` Michael Kerrisk
2008-02-13  0:18 ` [PATCH 1/3] syslog: Add type 10 Jeremy Kerr
2008-02-14 18:53   ` Michael Kerrisk
2008-02-13  0:18 ` [PATCH 3/3] syslog: document all type options Jeremy Kerr
2008-02-14 18:54   ` Michael Kerrisk [this message]
2008-02-14 18:53 ` [PATCH 0/3] syslog.2 updates Michael Kerrisk

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=47B48E4E.8080002@gmail.com \
    --to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=jk-mnsaURCQ41sdnm+yROfE0A@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