All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] cman: allow init script to pass options to fenced
Date: Tue, 16 Aug 2011 10:59:07 -0400	[thread overview]
Message-ID: <20110816145906.GD2421@redhat.com> (raw)
In-Reply-To: <1313473853-2929-1-git-send-email-fdinitto@redhat.com>

On Tue, Aug 16, 2011 at 07:50:53AM +0200, Fabio M. Di Nitto wrote:
> Use FENCED_OPTS to pass startup options to fenced
> 
> Resolves: rhbz#730639
> 
> Signed-off-by: Fabio M. Di Nitto <fdinitto@redhat.com>
> ---
>  cman/init.d/cman |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletions(-)
> 
> diff --git a/cman/init.d/cman b/cman/init.d/cman
> index b59216a..2ed83a5 100755
> --- a/cman/init.d/cman
> +++ b/cman/init.d/cman
> @@ -55,6 +55,9 @@
>  #     to join the fence domain (equivalent to "yes").
>  [ -z "$FENCE_JOIN" ] && FENCE_JOIN="yes"
>  
> +# FENCED_OPTS -- allow extra options to be passed to fence daemon.
> +[ -z "$FENCED_OPTS" ] && FENCED_OPTS=""
> +
>  # NETWORK_BRIDGE_SCRIPT -- script to use for xen network bridging.
>  #     This script must exist in the /etc/xen/scripts directory.
>  #     The default script is "network-bridge".
> @@ -163,7 +166,7 @@ start_daemons()
>  
>      status fenced &> /dev/null
>      if [ $? -ne 0 ]; then
> -	errmsg=$( /sbin/fenced 2>&1 ) || return 1
> +	errmsg=$( /sbin/fenced "$FENCED_OPTS" 2>&1 ) || return 1
>      fi
>  
>      status dlm_controld &> /dev/null

This looks fine by me.


-- 
Lon Hohberger - Red Hat, Inc.



      reply	other threads:[~2011-08-16 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16  5:50 [Cluster-devel] [PATCH] cman: allow init script to pass options to fenced Fabio M. Di Nitto
2011-08-16 14:59 ` Lon Hohberger [this message]

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=20110816145906.GD2421@redhat.com \
    --to=lhh@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.