From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] logsys in fenced
Date: Wed, 25 Jun 2008 12:30:00 -0500 [thread overview]
Message-ID: <20080625173000.GD18958@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806251857440.27368@trider-g7>
On Wed, Jun 25, 2008 at 07:04:15PM +0200, Fabio M. Di Nitto wrote:
> Our stack is absolutely impossible to debug as it is. There is a different
> debugging method and system for every single piece of code in the stack.
> It is a nightmare for people that wants to gather debugging output for us
> and send us logs.
>
> Your way:
>
> - learn every single debugging options for every single subsystem and
> command and maybe you will be able to find the data we need to help you
> because they are spreaded across logging files, syslogs and maybe stderr.
>
> My way:
>
> - add debug=on on the logging system. tar /var/log/cluster. done.
>
> While I respect that your idea of debugging is different, can you at least
> see the benefits for a one line change in a macro?
OK, once log_debug is back to the way it was, then I'll look into how to
direct debug statements to logsys in a way that's acceptable to me.
next prev parent reply other threads:[~2008-06-25 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 4:25 [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.05-9-g95a5c6b fabbione
2008-06-25 14:43 ` [Cluster-devel] logsys in fenced David Teigland
2008-06-25 14:53 ` Christine Caulfield
2008-06-25 15:55 ` David Teigland
2008-06-25 16:12 ` Steven Dake
2008-06-25 16:19 ` Fabio M. Di Nitto
2008-06-25 16:50 ` David Teigland
2008-06-25 17:04 ` Fabio M. Di Nitto
2008-06-25 17:30 ` David Teigland [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-25 21:21 David Teigland
2008-06-26 3:48 ` Fabio M. Di Nitto
2008-06-26 14:05 ` David Teigland
2008-06-27 3:45 ` Fabio M. Di Nitto
2008-06-27 15:12 ` Fabio M. Di Nitto
2008-06-26 21:43 ` David Teigland
2008-06-27 15:06 ` David Teigland
2008-06-27 15:16 ` Fabio M. Di Nitto
2008-06-28 3:27 ` Joel Becker
2008-06-28 3:50 ` Steven Dake
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=20080625173000.GD18958@redhat.com \
--to=teigland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).