All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: multipath-tools release coming
Date: Mon, 09 Dec 2013 13:31:36 +0100	[thread overview]
Message-ID: <52A5B828.408@suse.de> (raw)
In-Reply-To: <CABr-GncQNY=F8RuvqQ1ycVtHZdy6QDU9hLr3Uz=ZvLUadv9KFA@mail.gmail.com>

On 12/07/2013 07:48 AM, Christophe Varoqui wrote:
> Ben,
> 
> do you still have issues with the watchdog part of Hannes patchset ?
> If so, may be we can make it activable by a multipathd start-up
> parameter set in the the unit file command.
> 
Sadly, it's not that easy.

Whenever the user enables the watchdog feature via the systemd
unit file the program _has_ to respond to it; otherwise it'll
be stopped

So the watchdog integration has to stay, but we can make that
optional from the code if no watchdog functionality has been
requested from systemd.

That way the code will run unaffected and the watchdog-specific
parts will only be used when the user has activated the watchdog
from the systemd unit file.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2013-12-09 12:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-01 22:31 multipath-tools release coming Xose Vazquez Perez
2013-12-02  6:57 ` Hannes Reinecke
2013-12-07  6:48   ` Christophe Varoqui
2013-12-09 12:31     ` Hannes Reinecke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-29 22:19 Christophe Varoqui

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=52A5B828.408@suse.de \
    --to=hare@suse.de \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-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: 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.