From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Colin McCabe <cmccabe@alumni.cmu.edu>,
Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [PATCHv2] cld: use XDR for all messages
Date: Tue, 09 Feb 2010 18:21:02 -0500 [thread overview]
Message-ID: <4B71EDDE.6070209@garzik.org> (raw)
In-Reply-To: <20100209161306.5e312b28@redhat.com>
On 02/09/2010 06:13 PM, Pete Zaitcev wrote:
> On Tue, 09 Feb 2010 04:38:21 -0500
> Jeff Garzik<jeff@garzik.org> wrote:
>> On 02/09/2010 04:20 AM, Jeff Garzik wrote:
>
>>> Useful per-packet cld [the daemon] verbose output seems to have
>>> disappeared? Or did I miss a knob somewhere?
>>
>> cldcli no longers dumps per-packet debug info at maximum verbosity,
>> either. Our built-in debug facilities have definitely regressed.
>
> I posted the patch for both server and client, which should fix it.
> Looks like we became confused about what the exact meaning for
> log.verbose is, since historically we had 2: one means
> "enable LOG_DEBUG" and the other "enable per-packet dumping"
> (which is really verbose in normal operation). So the patch
> splits the two, thus permitting cldcli to control verbosity
> precisely. And no more commented-out assignments.
Actually it should be as presented in "cld --help" and "cldcli --help":
an integer, whose increasing value indicates increasing verbosity.
Higher values enable really verbose output, such as per-packet output.
So, the programs themselves have it right -- debug/verbose is an integer
not a bool. The internal libraries get that wrong sometimes, though.
Having separate knobs for 'debug' and 'verbose' will be more confusing
than a single control, IMO.
Jeff
next prev parent reply other threads:[~2010-02-09 23:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 17:49 [PATCHv2] cld: use XDR for all messages Colin McCabe
2010-01-21 1:38 ` Jeff Garzik
2010-01-21 2:38 ` Colin McCabe
2010-01-26 21:22 ` Colin McCabe
2010-01-26 22:11 ` Jeff Garzik
2010-01-26 23:47 ` Colin McCabe
2010-01-29 7:01 ` Jeff Garzik
2010-01-30 1:01 ` Colin McCabe
2010-02-03 6:35 ` [PATCH] " Jeff Garzik
2010-02-03 21:45 ` Colin McCabe
2010-02-05 9:51 ` Jeff Garzik
2010-02-05 0:59 ` Jeff Garzik
2010-02-05 4:14 ` Pete Zaitcev
2010-02-05 6:06 ` Jeff Garzik
2010-02-05 7:16 ` Pete Zaitcev
2010-02-05 9:48 ` Jeff Garzik
2010-02-05 18:49 ` Colin McCabe
2010-02-09 9:20 ` Jeff Garzik
2010-02-09 9:38 ` Jeff Garzik
2010-02-09 15:47 ` Pete Zaitcev
2010-02-09 23:13 ` Pete Zaitcev
2010-02-09 23:21 ` Jeff Garzik [this message]
2010-02-10 0:21 ` Pete Zaitcev
2010-02-10 1:33 ` Jeff Garzik
2010-02-10 2:27 ` Colin McCabe
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=4B71EDDE.6070209@garzik.org \
--to=jeff@garzik.org \
--cc=cmccabe@alumni.cmu.edu \
--cc=hail-devel@vger.kernel.org \
--cc=zaitcev@redhat.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 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.