All of lore.kernel.org
 help / color / mirror / Atom feed
From: "michael@kmaclub.com" <michael@kmaclub.com>
To: autofs@linux.kernel.org
Subject: Re: Making "verbose" mode a little less verbose
Date: Tue, 20 Jul 2010 07:50:22 -0700	[thread overview]
Message-ID: <4C45B7AE.7050906@kmaclub.com> (raw)
In-Reply-To: <20100706181115.GA23693@libre.l.ngdn.org>

On 07/06/2010 11:11 AM, Leonardo Chiquitto wrote:
> Hello AutoFS developers,
>
> I'm trying to improve the usefulness of "verbose" logs for a customer.
> The problem they currently face can be summarized as: they need some
> messages that are only logged with DEFAULT_LOGGING="verbose" (or debug),
> but enabling the verbose mode on busy servers (hundreds of users and
> AutoFS mount points) causes a significant traffic increase on their
> syslog infrastructure.
>
> My first idea was to introduce a new log level ("normal") and move the
> most important messages from "verbose" to "normal", but I realized later
> that this would require some redesign to allow some info() messages to
> be printed only on "verbose" mode. Since this would be more intrusive,
> I decided to go with a simpler proposal: move some "verbose" messages
> to "debug" level. Here are some examples of messages that would be
> demoted to debug (prefixed with -):


Hi Ian and Leonardo,

I am seeing a similar issue with my clients as well.  Autofs logs quite 
a bit of data and I would like to reduce it.  Turning off logging isn't 
an option since it is useful for debugging sporadic issues.

Would this patch be considered?  Is there some other way to reduce 
logging while still retaining enough to debug problems ( where running 
in debug mode isn't possible )?

Michael

  reply	other threads:[~2010-07-20 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 18:11 Making "verbose" mode a little less verbose Leonardo Chiquitto
2010-07-20 14:50 ` michael [this message]
2010-07-21  4:36 ` Ian Kent
2010-07-22 19:55   ` Leonardo Chiquitto
2010-07-23  5:36     ` 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=4C45B7AE.7050906@kmaclub.com \
    --to=michael@kmaclub.com \
    --cc=autofs@linux.kernel.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 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.