You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2013/10/17 23:43:53 UTC

[jira] [Commented] (BIGTOP-1096) alternatives within the alternatives-managed sub-directory could be harmful

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

Roman Shaposhnik commented on BIGTOP-1096:
------------------------------------------

+1

> 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
>            Assignee: Sean Mackrory
>            Priority: Blocker
>             Fix For: 0.7.0
>
>         Attachments: 0001-BIGTOP-1096.-alternatives-within-the-alternatives-ma.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)