All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] ocf resource invoking non-existent 'syncer' command
Date: Thu, 3 Jul 2014 15:33:28 +0200	[thread overview]
Message-ID: <20140703133328.GH11700@soda.linbit> (raw)
In-Reply-To: <201407021549.52105.mmazur@kernel.pl>

On Wed, Jul 02, 2014 at 03:49:51PM +0200, Mariusz Mazur wrote:
> drbdadm's 'syncer' command was removed in 8.4. Yet 
> thecreate_device_udev_settle() function in scripts/drbd.ocf still (as of 
> current git master branch) invokes it as have all the 8.4.x releases.
> 
> (I'm surprised nobody encountered this before, 8.4.0 is three years old.)

That's because it is *intentional*
(backwards compatibility).

If you look there, that's in an elif branch.

Cheers,
	Lars

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

      reply	other threads:[~2014-07-03 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 13:49 [Drbd-dev] ocf resource invoking non-existent 'syncer' command Mariusz Mazur
2014-07-03 13:33 ` Lars Ellenberg [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=20140703133328.GH11700@soda.linbit \
    --to=lars.ellenberg@linbit.com \
    --cc=drbd-dev@lists.linbit.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.