From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "WANG Cong" <wcong@critical-links.com>
Cc: mtk.manpages@gmail.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] Add the ENOSYS description for syslog(2)
Date: Fri, 20 Jun 2008 09:51:15 +0200 [thread overview]
Message-ID: <cfd18e0f0806200051u63ecdda0qccfcf5af0f9b1d58@mail.gmail.com> (raw)
In-Reply-To: <20080619172932.0509e359@hack>
On Thu, Jun 19, 2008 at 6:29 PM, WANG Cong <wcong@critical-links.com> wrote:
>
> Hi, Michael!
>
> syslog(2) just returns ENOSYS when CONFIG_PRINTK is not enabled.
> This should be described in man pages, I think.
>
> Patch is below.
>
> Thanks.
>
> Sigend-off-by: WANG Cong <wcong@critical-links.com>
Thanks! I've rewritten the text a bit, and applied this change for
man-pages-3.01.
Cheers,
Michael
> ---
> diff -Nrup man-pages-3.00/man2/syslog.2 man-pages-3.00.modified/man2/syslog.2
> --- man-pages-3.00/man2/syslog.2 2008-06-11 05:20:46.000000000 +0100
> +++ man-pages-3.00.modified/man2/syslog.2 2008-06-19 17:13:00.000000000 +0100
> @@ -235,6 +235,12 @@ capability).
> .B ERESTARTSYS
> System call was interrupted by a signal; nothing was read.
> (This can be seen only during a trace.)
> +.TP
> +.B ENOSYS
> +This system call is not enabled when the operating system
> +kernel was compiled.
> +The kernel configuration parameter controlling this is
> +.BR CONFIG_PRINTK .
> .SH "CONFORMING TO"
> This system call is Linux-specific and should not be used in programs
> intended to be portable.
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
prev parent reply other threads:[~2008-06-20 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 16:29 WANG Cong
2008-06-20 7:51 ` Michael Kerrisk [this message]
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=cfd18e0f0806200051u63ecdda0qccfcf5af0f9b1d58@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=wcong@critical-links.com \
/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
all inboxes | Powered by JetHome®