[
https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240088#comment-13240088
]
Roman Shaposhnik commented on BIGTOP-492:
-----------------------------------------
Guys, this whole thing is *really* quite simple. Basically, here's what I
propose to add to each of our launcher scripts *before* it execs the downstream
script:
{noformat}
[ -e /etc/bigtop/<component name>rc ] && . /etc/bigtop/<component name>rc
[ -e ~/.bigtop/<component name>rc ] && . /.bigtop/<component name>rc
{noformat}
Nothing more, nothing less. Very, very simple stuff.
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
> Key: BIGTOP-492
> URL: https://issues.apache.org/jira/browse/BIGTOP-492
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.4.0
>
>
> Almost all Unix (POSIX?) command line utilities have a nice feature of
> recognizing cascading defaults. The system-level one is typically named
> /etc/<util>rc and the user-level one is typically picked from ~/.<util>rc
> I propose that we introduce the same for all of the /usr/bin launcher scripts
> that we support in Bigtop. The proposed format of the rc files is that of
> POSIX-compatible sh(1) code snippet with an overall effect of exporting those
> variables that affect execution.
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
