From: "H. Peter Anvin" <hpa@zytor.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, viro@math.psu.edu
Subject: Re: klibc and logging
Date: Mon, 19 Aug 2002 10:27:59 -0700 [thread overview]
Message-ID: <3D612A9F.3080807@zytor.com> (raw)
In-Reply-To: 20020819182542.D17471@flint.arm.linux.org.uk
Russell King wrote:
> On Mon, Aug 19, 2002 at 09:58:02AM -0700, H. Peter Anvin wrote:
>
>>Either we can add a "syslog" binary, or you can:
>>
>>echo '<3>The dohickey is fscked' > /dev/kmsg
>
> Ok, that's fine for the echo-from-scripts problem. Now what if I bring
> in something like stderr of gzip? I suppose we need to modify all
> programs like gzip, etc to use syslog (maybe making perror() log to
> syslog)?
>
We need to think carefully about it. perror() and the likes are meant
to be taken in the context of having just executed a command, whereas a
syslog message needs to make sense on its own. That's part of why I
think making it stderr default is a bad idea.
-hpa
next prev parent reply other threads:[~2002-08-19 17:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 7:12 klibc and logging H. Peter Anvin
2002-08-13 7:52 ` Erik Andersen
2002-08-13 8:04 ` Alexander Viro
2002-08-13 10:12 ` Erik Andersen
2002-08-13 10:38 ` Alexander Viro
2002-08-13 14:27 ` Eric W. Biederman
2002-08-13 18:05 ` H. Peter Anvin
2002-08-13 9:42 ` Miquel van Smoorenburg
2002-08-13 17:41 ` H. Peter Anvin
2002-08-13 17:54 ` Benjamin LaHaise
2002-08-13 17:59 ` H. Peter Anvin
2002-08-13 17:55 ` Randy.Dunlap
2002-08-16 5:05 ` Oliver Xymoron
2002-08-19 13:27 ` Russell King
2002-08-19 13:59 ` H. Peter Anvin
2002-08-19 16:54 ` Russell King
2002-08-19 16:58 ` H. Peter Anvin
2002-08-19 17:25 ` Russell King
2002-08-19 17:27 ` H. Peter Anvin [this message]
2002-08-19 17:29 ` H. Peter Anvin
2002-08-19 19:37 ` Alan Cox
2002-08-19 19:40 ` H. Peter Anvin
2002-08-20 13:22 ` Thunder from the hill
2002-08-20 14:45 ` Russell King
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=3D612A9F.3080807@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.