From: Lars Ellenberg <Lars.Ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] DRBD8: drbdadm can't stat drbdsetup/drbdmeta
Date: Fri, 1 Dec 2006 19:36:32 +0100 [thread overview]
Message-ID: <20061201183632.GE7942@soda.linbit> (raw)
In-Reply-To: <BD7042533C2F8943A6A4257A9E31C45439C852@EXNA.corp.stratus.com>
/ 2006-12-01 09:17:36 -0500
\ Montrose, Ernest:
> Hi all,
> Looks like a bug was introduced where unless drbdadm is invoqued with
> the full path, it complains this way:
> "stat() of drbdsetup/drbmeta failed: no such file or directory."
> I am not sure why we don't just let the exec fail instead of verifying
> ahead.
> See sanity_check_cmd() and sanity_check_perm() in user/drbdadm_main.c.
reason is: we want to verify the validity of the configuration.
if you configure an outdate peer handler (and use our heartbeat plugin
implementation dopd), you must have the permissions set like that,
otherwise the configuration won't work as expected.
we probably should add "--check-perms" to both drbdmeta and drbdsetup,
and let drbdadm _call_ them via exec, instead of iterating over $PATH
ourselves...
and I think it should not exit(10) if stat does not work, anyways,
since the other thing is a warning only, too.
--
: Lars Ellenberg Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com :
prev parent reply other threads:[~2006-12-01 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 14:17 [Drbd-dev] DRBD8: drbdadm can't stat drbdsetup/drbdmeta Montrose, Ernest
2006-12-01 18:36 ` 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=20061201183632.GE7942@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox