All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Lang <sam.lang@inktank.com>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: Joe Buck <jbbuck@gmail.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Proposed change to vstart.sh
Date: Tue, 23 Oct 2012 06:46:13 -0500	[thread overview]
Message-ID: <50868385.7090708@inktank.com> (raw)
In-Reply-To: <CAC-hyiHFiryTZYi_wC_BswcK49k_ek346o1qhu6NPZDTquPuQg@mail.gmail.com>

On 10/22/2012 11:28 AM, Yehuda Sadeh wrote:
> On Mon, Oct 22, 2012 at 9:19 AM, Sam Lang <sam.lang@inktank.com> wrote:
>> On 10/22/2012 11:14 AM, Yehuda Sadeh wrote:
>>>
>>> On Mon, Oct 22, 2012 at 9:08 AM, Sam Lang <sam.lang@inktank.com> wrote:
>>>>
>>>> On 10/22/2012 10:13 AM, Joe Buck wrote:
>>>>>
>>>>>
>>>>> On 10/21/2012 02:35 PM, Sage Weil wrote:
>>>>
>>>>
>>>>
>>>>>> Also, we should fix the auth none usage at some point.  :)
>>>>
>>>>
>>>>
>>>> I made some changes a while back to fix the auth none problems with
>>>> vstart
>>>>
>>>> (https://github.com/ceph/ceph/commit/0f7c516f3e1f37c5869f8fbff67f53ca0c90568c).
>>>> The -x help text inversion was a bug on my part.
>>>>
>>>
>>> By the way, I think those changes broke the use of CEPH_BIN env variable.
>>
>>
>> I may not be using CEPH_BIN as intended then.  What is CEPH_BIN supposed to
>> point to?
>>
>> I usually setup out-of-tree builds, and point CEPH_BIN at the src dir there:
>>
>> <in ceph dir>
>> mkdir build
>> cd build
>> ../configure ...
>> make
>> CEPH_BIN=$PWD/src
>> ../src/vstart.sh ...
>>
> CEPH_BIN should point at the built binaries. I usually set up out of
> tree builds also, and point CEPH_BIN at the make install target, which
> should also work. Maybe vstart.sh misuses it (e.g., looks at CEPH_BIN
> for some other dependency).

It was previously doing ./init-ceph (which only worked if run from the 
ceph srcdir), and now does $CEPH_BIN/init-ceph, which breaks when you 
point CEPH_BIN at the make install target.

My goal with that change was to be able to run vstart.sh from outside 
the src dir (namely from the build dir).  To do that though, I think we 
would need to turn it into a autoconf generated file (vstart.sh.in -> 
vstart.sh).  That doesn't seem worth the trouble.  I'll put the 
./init-ceph back in.

-sam

>


  reply	other threads:[~2012-10-23 11:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-21 21:31 Proposed change to vstart.sh Joe Buck
2012-10-21 21:35 ` Sage Weil
2012-10-22  6:05   ` Dan Mick
2012-10-22 15:13   ` Joe Buck
2012-10-22 16:08     ` Sam Lang
2012-10-22 16:14       ` Yehuda Sadeh
2012-10-22 16:19         ` Sam Lang
2012-10-22 16:28           ` Yehuda Sadeh
2012-10-23 11:46             ` Sam Lang [this message]
2012-10-22 16:35       ` Joe Buck
2012-10-22 16:40         ` Sage Weil
2012-10-23  5:22           ` Dan Mick
2012-10-22 17:54         ` Sam Lang
2012-10-22 18:07           ` Joe Buck

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=50868385.7090708@inktank.com \
    --to=sam.lang@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jbbuck@gmail.com \
    --cc=yehuda@inktank.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.