[
https://issues.apache.org/jira/browse/BIGTOP-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701470#comment-13701470
]
Sean Mackrory commented on BIGTOP-939:
--------------------------------------
{quote}
Why not having a static symlink to /etc and have people use alternatives to
switch between ssh/no-ssl configs?
{quote}
Mainly just because I'd like to avoid shipping multiple sets of configs. I
think it's a necessity with the SSL situation because users shouldn't edit
stuff in /usr, but if we *really* don't like the way I've done the SSL support,
I think I'd rather have users make the necessary changes in /etc themselves
than use alternatives - but yeah that would certainly be technically doable.
{quote}
Shouldn't the rm command have also a -f parameter?
{quote}
Yeah. Hasn't caused a problem for me yet, but that's probably good to have.
Will add to the patch...
> Make usage of bigtop-tomcat more dynamic
> ----------------------------------------
>
> Key: BIGTOP-939
> URL: https://issues.apache.org/jira/browse/BIGTOP-939
> Project: Bigtop
> Issue Type: Task
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments:
> 0001-BIGTOP-939.-Make-usage-of-bigtop-tomcat-more-dynamic.patch,
> 0001-BIGTOP-939.-Make-usage-of-bigtop-tomcat-more-dynamic.patch
>
>
> Projects like Oozie and Sqoop present some configuration challenges compared
> to other components because they use Tomcat. Sometimes small tweaks to the
> configuration or classpath have to be done in a very component-specific way
> as opposed to tweaking files in /etc/<comp>/conf or /etc/default. In one
> case, we even have redundant Tomcat deployments for common configurations
> (Oozie's SSL vs. non-SSL).
> If the environment for Tomcat was generated more dynamically, we could avoid
> this redundancy and could allow common features to be configured in more
> "standard" ways.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
