All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] logsys in fenced
Date: Wed, 25 Jun 2008 09:43:44 -0500	[thread overview]
Message-ID: <20080625144343.GA18958@redhat.com> (raw)
In-Reply-To: <20080625042547.24195.qmail@sourceware.org>

> commit 95a5c6b13294742956b13070ebc4f4513278255f
> Author: Fabio M. Di Nitto <fdinitto@redhat.com>
> Date:   Wed Jun 25 06:24:11 2008 +0200
> 
>     [FENCE] fenced: separate concept of fork and debugging
>     
>     allow fenced to fork when debugging is set from the configuration
>     or the system will hang at boot.
>     
>     Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
> 
> commit da704715c606c9c01637ae53d79f8dec6a8b0389
> Author: Fabio M. Di Nitto <fdinitto@redhat.com>
> Date:   Wed Jun 25 05:19:35 2008 +0200
> 
>     [FENCE] Allow fenced to configure logsys
>     
>     Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
> 
> commit 18e085596bb8844f74689a92662f2e5e9166836b
> Author: Fabio M. Di Nitto <fdinitto@redhat.com>
> Date:   Wed Jun 25 04:49:41 2008 +0200
> 
>     [FENCE] Move logsys configuration calls where they belong
>     
>     Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
> 
> commit c54c56c5a09f98547ceda3bc5fa9afa28b354480
> Author: Fabio M. Di Nitto <fdinitto@redhat.com>
> Date:   Wed Jun 25 04:23:20 2008 +0200
> 
>     [FENCE] Make fenced ready to load logsys config
>     
>     Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
> 
> commit cf4c7ebac813b0b607acf6cf74bbdddfc8cfb12a
> Author: Fabio M. Di Nitto <fdinitto@redhat.com>
> Date:   Tue Jun 24 14:34:35 2008 +0200
> 
>     [FENCE] Start porting fenced to logsys
>     
>     Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>

OK, I'm fine with replacing the use of syslog with logsys, but this goes
beyond that.  Here are the problems I see:


. Leave log_debug() unchanged, and leave the meaning/effect of -D unchanged.
  syslog/logsys are about logging to files.  The debug "logging" I use is
  about logging to either an in-memory buffer or to stderr; syslog/logsys
  are not relevant to that.


. Change log_error() to use logsys instead of syslog, i.e. don't change
  the existing log_error() call sites.

  #define log_error(fmt, args...) \
  do { \
	log_debug(fmt, ##args); \
  -	syslog(LOG_ERR, fmt, ##args); \
  + 	log_printf(LOG_ERR, fmt, ##args); \
  } while (0)


. Finally, one gripe with logsys itself.  Here's syslog initialization:

  openlog("fenced", LOG_PID, LOG_DAEMON);

  Compare with logsys initialization:

  LOGSYS_DECLARE_SYSTEM (NULL,
  	LOG_MODE_OUTPUT_STDERR | LOG_MODE_OUTPUT_SYSLOG_THREADED | 
	LOG_MODE_OUTPUT_FILE | LOG_MODE_BUFFER_BEFORE_CONFIG,
	LOGDIR "/fenced.log",
	SYSLOGFACILITY);
  LOGSYS_DECLARE_SUBSYS ("FENCED", LOG_LEVEL_INFO);

  ...

  logsys_config_mode_set(LOG_MODE_OUTPUT_STDERR |
	LOG_MODE_OUTPUT_SYSLOG_THREADED | LOG_MODE_OUTPUT_FILE | 
	LOG_MODE_FLUSH_AFTER_CONFIG);

  ... and at the start of every other file:

  LOGSYS_DECLARE_SUBSYS ("FENCED", LOG_LEVEL_INFO);

  This really gets out of hand.  I'd like to see the initialization wrapped
  into a single function call, and the macros at the start of every file
  unnecessary.
 



  reply	other threads:[~2008-06-25 14:43 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 ` David Teigland [this message]
2008-06-25 14:53   ` [Cluster-devel] logsys in fenced 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
  -- 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=20080625144343.GA18958@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 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.