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

["Sean Mackrory (JIRA)" <ji...@apache.org>]

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

Sean Mackrory commented on BIGTOP-1096:
---------------------------------------

Since the second level alternatives point to the top level symlink (e.g. /etc/oozie/conf) the actual file it points to shouldn't ever be a broken symlink, unless tomcat_deployment does not exist under whatever new configuration they point to. The only way I see that happening accidentally is if a user who has already changed which configuration the symlink points to upgrades. In which case, I think they'll just need to add the new configuration directory, just like they would need to with any new configuration file. We should definitely document that in a "release note" or something, but am I missing a bigger problem?
                
> 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