public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: rmccabe@sourceware.org To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com Subject: Cluster Project branch, master, updated. gfs-kernel_0_1_22-48-g01c2c77 Date: Fri, 29 Feb 2008 17:32:00 -0000 [thread overview] Message-ID: <20080229173246.27623.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Cluster Project". http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=01c2c77a02deb7ae01c37d7e68df6cde608ed2a9 The branch, master has been updated via 01c2c77a02deb7ae01c37d7e68df6cde608ed2a9 (commit) via e661e099a462b452c443eb83de4046c335b473be (commit) from 8e504af1adbadd2cb8fe7cab191d79a8d835540c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 01c2c77a02deb7ae01c37d7e68df6cde608ed2a9 Merge: e661e099a462b452c443eb83de4046c335b473be 8e504af1adbadd2cb8fe7cab191d79a8d835540c Author: Ryan McCabe <rmccabe@redhat.com> Date: Fri Feb 29 12:32:39 2008 -0500 Merge branch 'master' of ssh://sources.redhat.com/git/cluster commit e661e099a462b452c443eb83de4046c335b473be Author: Ryan McCabe <rmccabe@redhat.com> Date: Fri Feb 29 12:32:03 2008 -0500 Fix a few misspellings ----------------------------------------------------------------------- Summary of changes: fence/man/fenced.8 | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/fence/man/fenced.8 b/fence/man/fenced.8 index 91eb510..991cd83 100644 --- a/fence/man/fenced.8 +++ b/fence/man/fenced.8 @@ -71,7 +71,7 @@ it) and subsequently enabled (by the cluster gaining quorum) any nodes listed in cluster.conf that are not presently members of the cman cluster are fenced. The status of these nodes is unknown, and to be on the side of safety they are assumed to be in need of fencing. This startup fencing -can be disabled, but it's only truely safe to do so if an operator is +can be disabled, but it's only truly safe to do so if an operator is present to verify that no cluster nodes are in need of fencing. This example illustrates why startup fencing is important. Take a three @@ -119,7 +119,7 @@ continue without fencing the node. Fencing daemon behavior can be controlled by setting options in the cluster.conf file under the section <fence_daemon> </fence_daemon>. See above for complete descriptions of these values. The delay values are in -seconds; -1 secs means an unlimitted delay. The values shown are the +seconds; -1 secs means an unlimited delay. The values shown are the defaults. Post-join delay is the number of seconds the daemon will wait before @@ -267,7 +267,7 @@ Find documentation for configuring specific devices at http://sources.redhat.com/cluster/ .SH OPTIONS -Command line options override corresonding values in cluster.conf. +Command line options override corresponding values in cluster.conf. .TP \fB-j\fP \fIsecs\fP Post-join fencing delay hooks/post-receive -- Cluster Project
reply other threads:[~2008-02-29 17:32 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080229173246.27623.qmail@sourceware.org \ --to=rmccabe@sourceware.org \ --cc=cluster-cvs@sources.redhat.com \ --cc=cluster-devel@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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).