[
https://issues.apache.org/jira/browse/BIGTOP-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778038#comment-13778038
]
Roman Shaposhnik commented on BIGTOP-1096:
------------------------------------------
Here's what I'm talking about:
{noformat}
# apt-get install oozie
# cp -r /etc/oozie/conf.dist /etc/oozie/conf.mycluster
# update-alternatives --install /etc/oozie/conf oozie-conf
/etc/oozie/conf.mycluster 100
update-alternatives: using /etc/oozie/conf.mycluster to provide /etc/oozie/conf
(oozie-conf) in auto mode
{noformat}
At this point we get into a very confusing situation wrt. where the tomcat-conf
is picked from
> 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
