You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Ellen Evans (JIRA)" <ji...@apache.org> on 2013/07/01 19:00:22 UTC

[jira] [Commented] (AMBARI-2523) Change wording's of various notfications/messages in Ambari Setup so that users are not alarmed.

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

Ellen Evans commented on AMBARI-2523:
-------------------------------------

Currently the docs say this:
Permanently disabling SELinux so that on system reboot it does not restart is strongly recommended. To do this, edit the SELinux config and set SELINUX to disabled. On each host:
vi /etc/selinux/config

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#       permissive - SELinux prints warnings instead of enforcing.
#       disabled - SELinux is fully disabled.
SELINUX=disabled 
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
SELINUXTYPE=targeted

Does this need to be changed?
                
> Change wording's of various notfications/messages in Ambari Setup so that users are not alarmed.
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-2523
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2523
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.2.5
>            Reporter: Mahadev konar
>            Assignee: Mahadev konar
>             Fix For: 1.2.5
>
>         Attachments: AMBARI-2523.patch
>
>
> Change wording's of various notfications/messages in Ambari Setup so that users are not alarmed.
> * Do not suggest to permanently disable SELinux
> * setup says "Create a separate user for ambari-server daemon" (we should
> instead say "Use a separate user X as user may not need to be created as
> it exists)
> * setup says "IPTables is disabled now" - We should add, you should
> reenable it after setup

--
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