[
https://issues.apache.org/jira/browse/BIGTOP-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated BIGTOP-988:
---------------------------------
Attachment: 0001-BIGTOP-988.-HCatalog-does-not-launch-daemon-process-.patch
That approach worked quite well. I tried both the HCatalog and HDFS NameNode
init scripts. /proc/.../cwd was correct for all the processes. Services that
override the start function will need to do this themselves, but AFAIK, they
all do - and I agree with your suggestion - they all should continue to do so.
> HCatalog does not launch daemon process in a known directory
> ------------------------------------------------------------
>
> Key: BIGTOP-988
> URL: https://issues.apache.org/jira/browse/BIGTOP-988
> Project: Bigtop
> Issue Type: Bug
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Blocker
> Attachments:
> 0001-BIGTOP-988.-HCatalog-does-not-launch-daemon-process-.patch
>
>
> HCatalog launches the process in the current working directory, after which
> files may be created in the wrong location, and the hcatalog user (hive) may
> not even have permissions there!
--
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
