[jira] [Commented] (BOOKKEEPER-329) provide stop scripts for hub server

["Ivan Kelly (JIRA)" <ji...@apache.org>]

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

Ivan Kelly commented on BOOKKEEPER-329:
---------------------------------------

The script doesn't work as I would expect it to (this also holds for bookkeeper-daemon.sh).

{quote}
$ sh hedwig-server/bin/hedwig-daemon.sh start
starting , logging to /Users/test/src/bookkeeper/hedwig-server/logs/hedwig--sweetgreat-lm.log
JMX enabled by default
Usage: hedwig <command>
where command is one of:
    server           Run the hedwig server
    console          Run the hedwig admin console
    help             This help message

or command is the full name of a class with a defined main() method.

Environment variables:
{quote}

Being a daemon only makes sense for the server command, in this case, and in the bookkeeper case.  The behaviour I expect from this script is that I run:
{quote}
$ bin/hedwig-daemon.sh start
{quote}
and the daemon starts. 

I run
{quote}
$ bin/hedwig-daemon.sh stop
{quote}
and the daemon stops.

There should not be any other commandline arguments. Any configuration should be through hwenv.sh. Could you make the same changes for bookkeeper-daemon.sh also? 
                
> provide stop scripts for hub server
> -----------------------------------
>
>                 Key: BOOKKEEPER-329
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-329
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-server
>    Affects Versions: 4.0.0, 4.1.0
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-329.diff
>
>
> as what we did in BOOKKEEPER-296, it would be better to provide similar script to start/stop hub server.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira