[
https://issues.apache.org/jira/browse/ZOOKEEPER-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533843#comment-13533843
]
Hudson commented on ZOOKEEPER-1335:
-----------------------------------
Integrated in ZooKeeper-trunk #1775 (See
[https://builds.apache.org/job/ZooKeeper-trunk/1775/])
ZOOKEEPER-1335. Add support for --config to zkEnv.sh to specify a config
directory different than what is expected (Arpit Gupta via mahadev) (Revision
1422758)
Result = SUCCESS
mahadev :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1422758
Files :
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/bin/zkEnv.sh
* /zookeeper/trunk/bin/zkServer.sh
> Add support for --config to zkEnv.sh to specify a config directory different
> than what is expected
> --------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1335
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1335
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1335.patch, ZOOKEEPER-1335.patch
>
>
> zkEnv.sh expects ZOOCFGDIR env variable set. If not it looks for the conf dir
> in the ZOOKEEPER_PREFIX dir or in /etc/zookeeper. It would be great if we can
> support --config option where at run time you could specify a different
> config directory. We do the same thing in hadoop.
> With this you should be able to do
> /usr/sbin/zkServer.sh --config /some/conf/dir start|stop
--
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
