[
https://issues.apache.org/jira/browse/BIGTOP-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778335#comment-13778335
]
Sean Mackrory commented on BIGTOP-1096:
---------------------------------------
Personally I don't find it confusing because it will look under whatever the
current oozie config directory is. So
/etc/oozie/conf.mycluster/tomcat-deployment would be used in this case. I
wouldn't be opposed to, say, making it a peer directory, if you think that
would be less confusing. So for all the components, tomcat configuration would
be copied from /etc/<component>/tomcat_deployment, and in Oozie's case that
would an alternatives symlink just like /etc/<component>/conf. If people seem
to find that more robust, I'll go ahead and implement / test that.
> alternatives within the alternatives-managed sub-directory could be harmful
> ---------------------------------------------------------------------------
>
> Key: BIGTOP-1096
> URL: https://issues.apache.org/jira/browse/BIGTOP-1096
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.7.0
> Reporter: Roman Shaposhnik
> Fix For: 0.8.0
>
>
> I see that Oozie (at least) today creates a second level alternatives managed
> subdir (tomcat conf) under something that is already managed by an
> alternatives mechanism (oozie conf). This looks like it could be a problem if
> the user switches the top level one (oozie conf).
--
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
