Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bigtop-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Fri, 7 Sep 2012 11:43:55 -0700
From: Konstantin Boudnik <cos@apache.org>
To: bigtop-dev@incubator.apache.org
Cc: Sean Mackrory <mackrorysd@gmail.com>
Subject: Re: running init.d scripts by hand vs. service(8)
Message-ID: <20120907184355.GV3169@tpx>
Mail-Followup-To: bigtop-dev@incubator.apache.org,
	Sean Mackrory <mackrorysd@gmail.com>
References: 
 <CA+ULb+uQ2cgjU_-6=E5mR76L+AdPN9OYVF7-LB+DQj=BzG1p7Q@mail.gmail.com>
 <20120906004118.GD12794@linspire.com>
 <CAJs-t7PAfv6HpJmuE7WEmg6hYOANP-kFMxWuAb3r_WnrR0rtUw@mail.gmail.com>
 <CA+ULb+sZcR7DpDMKM9rhHHWc+8-5V-QS-H_TdtP6C+sODk=erw@mail.gmail.com>
 <CAJs-t7PpFyPqDM264EnHammVhA1gaEF-0WJ0D-SwKXzsSRVicQ@mail.gmail.com>
 <CAGC+2Mv_pPHKODZ5AjXUQX4D2T75roq-rAo+06fp9syjJU3GvA@mail.gmail.com>
 <5049B510.5020608@apache.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="8VKnE9k7k7imdYv5"
Content-Disposition: inline
In-Reply-To: <5049B510.5020608@apache.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

--8VKnE9k7k7imdYv5
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 07, 2012 at 01:49AM, Bruno Mah=D0=98 wrote:
> On 09/06/2012 10:31 AM, Sean Mackrory wrote:
> >+1 to Alejandro's idea. I like the having the ability to manually overri=
de
> >environment variables and invoke scripts as a developer. I'd be annoyed =
if
> >I used a service and it refused to start up without service or if it
> >ignored my environment in an unnecessarily subtle way. That being said,
> >since one of the benefits of using Bigtop is more out-of-the-box
> >reliability and simplicity, I also like the idea of strongly encouraging
> >users to use 1 supported method of service invocation.
> >
> >On Thu, Sep 6, 2012 at 9:15 AM, Alejandro Abdelnur <tucu@cloudera.com>wr=
ote:
> >
> >>The verbosity would be there only when running the scripts outside of
> >>service, to avoid YOU tripping again :)
> >>
> >>On Thu, Sep 6, 2012 at 9:11 AM, Roman Shaposhnik <rvs@apache.org> wrote:
> >>>On Thu, Sep 6, 2012 at 8:14 AM, Alejandro Abdelnur <tucu@cloudera.com>
> >>wrote:
> >>>>I think is a desirable feature to be able to modify ENV then run start
> >>>>the daemon directly. It may be handy on troubleshooting.
> >>>
> >>>As I said -- it is entirely possible we can all agree that this is a
> >>feature.
> >>>
> >>>>I'd propose a modification to Cos' proposal, print a NICE BIG WARN
> >>>>when starting the daemons without service(8) stating 'current ENV
> >>>>settings may affect the daemon (Roman remember that)'
> >>>
> >>>I don't think I have a guaranteed way of detecting one vs. the other.
> >>>/usr/bin/service happens to be a shell script that at the end of the
> >>>day simply scrubs the environment and execs the actual init.d script:
> >>>     exec env -i LANG=3D"$LANG" PATH=3D"$PATH" TERM=3D"$TERM"
> >>>"$SERVICEDIR/$SERVICE" ${ACTION} ${OPTIONS}
> >>>
> >>>Perhaps we can try to detect that we're NOT exec'ed by service via
> >>>absence of things like HOME, etc.
> >>>
> >>>The question then becomes whether this is too much trouble and whether
> >>>it'll make our scripts too verbose.
> >>>
> >>>Thanks,
> >>>Roman.
> >>
> >>
> >>
> >>--
> >>Alejandro
> >>
> >
>=20
> These scripts could be called in various ways and I am a little bit
> worried about closing some doors.
> What about having a consistent behavior of always scrubbing the
> environment (so the script will always work by default), except when
> some debugging variable/parameter is passed to it.
> Hopefully people spend more time using these scripts than debugging them =
:)

Sounds good.

Cos

--8VKnE9k7k7imdYv5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iF4EAREIAAYFAlBKQGsACgkQenyFlstYjhJpfQEAs1cB69VAKKRn9R6CW937MO7K
zIhEGxfnIh9RzO4iZTwBAOA4eUrTw1H8HFOlP2sp56vVo4TaIcQkfi+pJgik+kAO
=qPPO
-----END PGP SIGNATURE-----

--8VKnE9k7k7imdYv5--