From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Teigland Date: Wed, 25 Jun 2008 12:30:00 -0500 Subject: [Cluster-devel] logsys in fenced In-Reply-To: References: <20080625042547.24195.qmail@sourceware.org> <20080625144343.GA18958@redhat.com> <20080625165045.GC18958@redhat.com> Message-ID: <20080625173000.GD18958@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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.