From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/ccs/daemon ccsd.c
Date: 16 Aug 2006 14:49:56 -0000 [thread overview]
Message-ID: <20060816144956.23111.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: STABLE
Changes by: teigland at sourceware.org 2006-08-16 14:49:56
Modified files:
ccs/daemon : ccsd.c
Log message:
(sync from RHEL4 branch)
don't grab random config from network, require initial cluster.conf file
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/ccs/daemon/ccsd.c.diff?cvsroot=cluster&only_with_tag=STABLE&r1=1.14.2.4.6.2&r2=1.14.2.4.6.3
--- cluster/ccs/daemon/ccsd.c 2006/01/11 16:03:10 1.14.2.4.6.2
+++ cluster/ccs/daemon/ccsd.c 2006/08/16 14:49:56 1.14.2.4.6.3
@@ -509,16 +509,28 @@
if(!stat(config_file_location, &stat_buf)){
doc = xmlParseFile(config_file_location);
if(!doc){
- log_err("\nUnable to parse %s.\n"
- "You should either:\n"
- " 1. Correct the XML mistakes, or\n"
- " 2. (Re)move the file and attempt to grab a "
- "valid copy from the network.\n", config_file_location);
+ log_err("\nUnable to parse %s.\n", config_file_location);
return -1;
}
xmlFreeDoc(doc);
} else {
- /* no cluster.conf file. This is fine, just need to get it from the network */
+ /*
+ * no cluster.conf file.
+ * We used to simply return 0 here and let go fetch a random
+ * conf file from the network. This worked well in environments
+ * that had only one cluster in broadcast range, but it has
+ * caused to much confusion when there is more than one cluster.
+ * Additionally, our docs and manuals tell users to copy the
+ * file to each node anyway.
+ *
+ * In the event that there is a cluster.conf file, ccs will
+ * still ensure that it has the most up-to-date copy of the
+ * file in relation to the other nodes in the quorate cluster.
+ */
+ log_err("%s: file not found.\n"
+ "Please ensure an initial copy of this file is present on all cluster nodes.\n",
+ config_file_location);
+ return -1;
}
return 0;
next reply other threads:[~2006-08-16 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 14:49 teigland [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-30 17:35 [Cluster-devel] cluster/ccs/daemon ccsd.c rohara
2006-08-31 17:49 rohara
2007-08-30 21:31 rmccabe
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=20060816144956.23111.qmail@sourceware.org \
--to=teigland@sourceware.org \
/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).