[
https://issues.apache.org/jira/browse/BIGTOP-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680781#comment-13680781
]
Mark Grover commented on BIGTOP-1006:
-------------------------------------
One solution is to be explicit about which directory to cd into when running
init scripts instead of simply relying on the home directory.
> Explicitly state the working directory to be used in init scripts instead of
> relying on user's home directories
> ---------------------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-1006
> URL: https://issues.apache.org/jira/browse/BIGTOP-1006
> Project: Bigtop
> Issue Type: Bug
> Components: Debian, RPM
> Affects Versions: 0.6.0
> Reporter: Mark Grover
> Assignee: Mark Grover
> Fix For: 0.7.0
>
>
> Presently, the init script template cd's into a working directory when
> running the init script (reference:
> https://github.com/apache/bigtop/blob/master/bigtop-packages/src/templates/init.d.tmpl#L86)
> When no such variable (WORKING_DIR) is provided when building the init
> script, it will default to the user in question's home directory.
> This can lead to problems in upgrade scenarios. Say the user "mapred" already
> exists (say because the user had an old or existing installation of Bigtop)
> and that user has a different working directory for the user that no longer
> exists.
> When Bigtop package installation occurs, it doesn't create the user if it
> already exists. In such a case, the init script fails because it can't cd
> into the home directory.
--
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
