incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Mahé (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (BIGTOP-492) make our launcher scripts recognize cascading defaults
Date Wed, 28 Mar 2012 01:05:22 GMT

    [ https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240086#comment-13240086
] 

Bruno Mahé commented on BIGTOP-492:
-----------------------------------

But in any case users will have to know which variable to export/override, no?
What layer of abstraction are you thinking about? How much complexity will be added?
                
> 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

       

Mime
View raw message