From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] ccs_config_dump / ccs_config_validate
Date: Tue, 8 Sep 2009 13:34:51 -0500 [thread overview]
Message-ID: <20090908183451.GB11641@redhat.com> (raw)
In-Reply-To: <1252428569.16393.11.camel@cerberus.int.fabbione.net>
On Tue, Sep 08, 2009 at 06:49:29PM +0200, Fabio M. Di Nitto wrote:
> did you try the -v option in the version I committed a few hours ago
> based on your previous suggestions? :)
>
> Skipping the rest of the email for obvious reasons :)))
>
> So unless I am missing something, the current implementation does
> exactly what you have been asking for.
Yes, I think it has all the capabilities we need, but the usage, options, and
output are still quite confusing. Here's what I'd like to see:
ccs_config_validate [options] [-f|-l] [/path/to/file]
Options:
-f /path/to/file Validate the config from the specified file.
-l [/path/to/file] Validate the config from the specified file
(or other source using /etc/sysconfig/cman),
after loading it into config libs which add
default values.
-v Produce verbose output
-d Produce debug output
-V Print program version information, then exit
-h Print this help, then exit
Debugging options:
-C config_loader Override config plugin loader
-t tempfile Force temporay file to tempfile
-n Do not remove temporary file
-o Overwrite temporary file (dangerous)
verbose option would add "test file" / "test load" output
> ccs_config_validate -v -f /path/to/file
test file /path/to/file
> ccs_config_validate -v -l /path/to/file
test load /path/to/file
> ccs_config_validate -v -l
test load [/path/to/file | ldap/url]
> ccs_config_validate -v
test load [/path/to/file | ldap/url]
debug option would add config libs and temp file output
> ccs_config_validate -v -d -l
test load [/path/to/file | ldap/url]
config libs [xmlconfig|ldapconfig]:cmanpreconfig
temporary file /tmp/tmp.cbtgJ20313
next prev parent reply other threads:[~2009-09-08 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 19:22 [Cluster-devel] ccs_config_dump / ccs_config_validate David Teigland
2009-09-04 6:16 ` Fabio M. Di Nitto
2009-09-04 15:37 ` David Teigland
2009-09-04 17:44 ` Fabio M. Di Nitto
2009-09-04 18:06 ` David Teigland
2009-09-05 6:12 ` Fabio M. Di Nitto
2009-09-07 6:42 ` Christine Caulfield
2009-09-08 16:01 ` David Teigland
2009-09-08 16:49 ` Fabio M. Di Nitto
2009-09-08 18:34 ` David Teigland [this message]
2009-09-08 20:47 ` Fabio M. Di Nitto
2009-09-08 20:50 ` Fabio M. Di Nitto
2009-09-09 15:42 ` David Teigland
2009-09-09 17:24 ` Fabio M. Di Nitto
2009-09-09 18:09 ` David Teigland
2009-09-09 18:37 ` Fabio M. Di Nitto
2009-09-10 8:22 ` Christine Caulfield
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=20090908183451.GB11641@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).