[
https://issues.apache.org/jira/browse/SINGA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942545#comment-14942545
]
Anh Dinh commented on SINGA-79:
-------------------------------
at the moment, the paths to "job.conf" and "singa.conf" are inferred from the
path of "run-singa.sh". But it's possible, especially in a cluster, that
"run-singa.sh" and other configs file don't share the same parent directory.
For example, given the following:
+ /root/dir1: job.conf
+ /root/dir2: singa.conf
+ /root/incubator-singa/bin/: run-singa.sh
it's not possible to run (throws error saying cannot find conf/singa.conf):
run-singa.sh -job /root/dir1/job.conf
Since singa.conf consists of only 2 flags, can we make the driver to parse them
from the command lines? Or alternatively, can we parse another flag
"-singa_conf" to the main function?
> Fix bug in singatool that can not parse -conf flag
> --------------------------------------------------
>
> Key: SINGA-79
> URL: https://issues.apache.org/jira/browse/SINGA-79
> Project: Singa
> Issue Type: Bug
> Reporter: Sheng Wang
> Assignee: Sheng Wang
>
> After the gflag is removed from our dependency, the -conf flag in tool.cc is
> not correctly parsed.
> It will make any executions that are not under SINGA_HOME fail to get the
> correct configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
