From: ramana <ramana@intraperson.com>
To: "Peter C. Norton" <spacey-autofs@lenin.net>
Cc: autofs@linux.kernel.org
Subject: Re: [PATCH 3/5] logging to stderr
Date: Mon, 14 Feb 2005 22:02:48 +0530 [thread overview]
Message-ID: <4210D2B0.9080601@intraperson.com> (raw)
In-Reply-To: <20050214160739.GH9056@lenin.net>
Peter C. Norton wrote:
>There are sometimes good reasons to log to stderr instead of syslog.
>syslog is slow, loses messages, inflexable, and can introduce delays
>and huge volumes of crap to the disk. Using stderr loggers can
>filter, or do things like rotate logs actively, etc.
>
>I don't know if any of these are the motivations for the patch, but if
>its not intrusive its a good idea.
>
>-Peter
>
>
>
I put this feature right from the beginning in Autodir, not intended for
above reasons but it helped and helps debugging many bugs.
Regards
ramana
--
http://www.intraperson.com
next prev parent reply other threads:[~2005-02-14 16:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 9:55 [PATCH 0/5] rediffed patches Denis Vlasenko
2005-02-11 9:58 ` [PATCH 1/5] use PATH Denis Vlasenko
2005-02-11 9:59 ` Denis Vlasenko
2005-02-11 10:01 ` [PATCH 2/5] add --foreground option Denis Vlasenko
2005-02-11 10:03 ` [PATCH 3/5] logging to stderr Denis Vlasenko
2005-02-11 10:06 ` [PATCH 4/5] switch to new logging Denis Vlasenko
2005-02-11 10:09 ` [PATCH 5/5] Denis Vlasenko
2005-02-14 15:21 ` [PATCH 3/5] logging to stderr Jeff Moyer
2005-02-14 16:07 ` Peter C. Norton
2005-02-14 16:21 ` Steinar H. Gunderson
2005-02-14 16:38 ` Peter C. Norton
2005-02-14 16:32 ` ramana [this message]
2005-02-15 1:26 ` Ian Kent
2005-02-15 13:28 ` Jeff Moyer
2005-02-15 14:32 ` raven
2005-02-15 15:29 ` Greg Wooledge
2005-02-13 12:26 ` [PATCH 0/5] rediffed patches raven
2005-02-13 13:25 ` raven
2005-02-13 13:42 ` Steinar H. Gunderson
2005-02-14 1:10 ` Ian Kent
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=4210D2B0.9080601@intraperson.com \
--to=ramana@intraperson.com \
--cc=autofs@linux.kernel.org \
--cc=spacey-autofs@lenin.net \
/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.