From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] logsys in cluster3
Date: Mon, 30 Jun 2008 10:23:01 -0500 [thread overview]
Message-ID: <20080630152301.GA31662@redhat.com> (raw)
Main points from the logsys discussion we had
- initialization: use functions instead of macros, don't always need
logging to be working from the start of execution, can wait until
function is called to start it, don't need notion of "subsystems"
or per-source-file logging features
- configuration setup: big blocks of setup code are repeated and largely
the same, make this less
- configuration changes: user should be able to change logging settings
in cluster.conf, propagate new cluster.conf, ccs should notify programs
of cluster.conf change, programs should reread whatever dynamic config
settings they use (may just be the logging settings), programs should
then change behavior according to the new settings
next reply other threads:[~2008-06-30 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 15:23 David Teigland [this message]
2008-06-30 16:38 ` [Cluster-devel] logsys in cluster3 Fabio M. Di Nitto
2008-06-30 17:31 ` David Teigland
2008-07-01 5:01 ` Fabio M. Di Nitto
2008-07-01 16:37 ` David Teigland
2008-07-01 17:21 ` David Teigland
2008-07-01 19:12 ` David Teigland
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=20080630152301.GA31662@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).