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

Roman Shaposhnik commented on BIGTOP-479:
-----------------------------------------

James, I agree with your general comment, but the question is -- what's the 
proper place to put the code that is supposed to su into the same user account 
that the daemons are running under? init.d scripts already know what that user 
account is (since they do the sudo to begin with) and it looks like nothing 
else does.

To take a step back -- we do provide wrappers for all of that init'ing, but 
they need to be run as follows:
{noformat}
  sudo -u <UID> <init-wrapper> <init-wrapper args>
{noformat}

I would like to hide the complexity of 'sudo -u <UID>' and <init-wrapper args> 
from the user and would appreciate suggestions on what the proper place for 
that would be.

For now, I'm attaching a patch for existing init.d scripts. We can always move 
that code to some other place.
                
> init.d scripts should provide an option for initializing persistent state of 
> the services that require it
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-479
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-479
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-479.patch.txt
>
>
> The following services require an explicit initialization of the persistent 
> state in the local filesystem:
>    # Hadoop NameNode (formatting a namenode via: hdfs namenode -format)
>    # ZooKeeper (formatting a local storage area via: 
> zookeeper-server-initialize)
> and the following ones require an initialization of the RDBMS database (which 
> can reside on a local filesystem
> via Derby or be hosted on a remote server such as Postgress, MySQL, Oracle, 
> etc.):
>    # oozie DB (initialized via ooziedb.sh)
>    # possible Hive metastore
>    # possibly Sqoop metastore
> In order to free the user from an explicit knowledge of what command to run 
> under which account it is desirable
> to have an init.d scripts for the above components support and extra command 
> called 'init'.
> Please let me know what do you all think.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to