Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Fri, 21 Jun 2013 14:40:19 +0000 (UTC)
From: "Dmitry Lysnichenko (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12653569.1371587957260.155187.1371825619951@arcas>
In-Reply-To: <JIRA.12653569.1371587957260@arcas>
References: <JIRA.12653569.1371587957260@arcas>
Subject: [jira] [Updated] (AMBARI-2423) Improvements to running Ambari
 Server as non-root
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Lysnichenko updated AMBARI-2423:
---------------------------------------

    Attachment: AMBARI-2423.patch
    
> Improvements to running Ambari Server as non-root
> -------------------------------------------------
>
>                 Key: AMBARI-2423
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2423
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.2.5
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 1.2.5
>
>         Attachments: AMBARI-2423.patch
>
>
> Improvements:
>     - We should rename ambari.user property to ambari-server.user
>     - For a user to change this user / group setting, I think we should provide a setup option because if they do change user / group, we also (probably) have to adjust directory and file permissions. And unless we document that (which we should do as well), they will likely just change the .user or .group property, then try to start server but server can't access what it might need.
>     - Looks like user check is performed after property import when performing "ambari-server start" as non-custom user.

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