You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "peng.jianhua (JIRA)" <ji...@apache.org> on 2017/03/14 03:26:41 UTC
[jira] [Updated] (RANGER-1449) There is logical inconsistency for
RANGER_PID_DIR_PATH in security admin
[ https://issues.apache.org/jira/browse/RANGER-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
peng.jianhua updated RANGER-1449:
---------------------------------
Attachment: 0001-RANGER-1449-There-is-logical-inconsistency-for-RANGE.patch
> There is logical inconsistency for RANGER_PID_DIR_PATH in security admin
> ------------------------------------------------------------------------
>
> Key: RANGER-1449
> URL: https://issues.apache.org/jira/browse/RANGER-1449
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Reporter: peng.jianhua
> Assignee: Qiang Zhang
> Priority: Minor
> Labels: patch
> Attachments: 0001-RANGER-1449-There-is-logical-inconsistency-for-RANGE.patch
>
>
> 1. There is RANGER_PID_DIR_PATH parameter in install.properties. But There is hard code at the begin of setup.sh
> pidFolderName='/var/run/ranger'
> mkdir -p ${pidFolderName}
> if [ ! $? = "0" ];then
> log "Make $pidFolderName failure....!!";
> exit 1;
> fi
> 2. The ranger-admin-services.sh will set default value and create default path when the RANGER_PID_DIR_PATH parameter is empty. The setup.sh doesn't set default value and create default path.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)