[ 
https://issues.apache.org/jira/browse/STORM-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984178#comment-13984178
 ] 

ASF GitHub Bot commented on STORM-283:
--------------------------------------

GitHub user ChitturiPadma opened a pull request:

    https://github.com/apache/incubator-storm/pull/95

    STORM-283 Support for config_value, running daemons in background

    Added fixes reading java.library.path from 
backtype.storm.command.config_value  and also the daemons nimbus/supervisor 
would run as backgorund processes

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ChitturiPadma/incubator-storm master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-storm/pull/95.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #95
    
----
commit 60fac27624611a5a25b3e2102149bff7f015293e
Author: ChitturiPadma <[email protected]>
Date:   2014-04-29T10:13:35Z

    storm-283 Support for config_value, running storm daemons in background

commit 442752b86647bd7a9ebf149dcbc6862fbb993911
Author: ChitturiPadma <[email protected]>
Date:   2014-04-29T10:16:54Z

    STORM-283 Support for config_value, running storm daemons as background 
process

----


> Support for config_value, running storm daemons in background
> -------------------------------------------------------------
>
>                 Key: STORM-283
>                 URL: https://issues.apache.org/jira/browse/STORM-283
>             Project: Apache Storm (Incubating)
>          Issue Type: New Feature
>         Environment: Windows
>            Reporter: Padma Priya Chitturi
>         Attachments: storm-278-patch.patch, storm-config-278-patch.patch
>
>
> storm.cmd doesn't read config values from storm.yaml file as there is no 
> support for config_value.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to