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

Camille Fournier commented on ZOOKEEPER-1535:
---------------------------------------------

OK patch #1 looks ok to me. It looks like this is leftover from some really old 
code refactorings that should have been removed when Henry put in 
ZOOKEEPER-386. I've tested the command line and it all looks good without this 
so I'm going to put it onto trunk and 3.4 for good measure.
                
> ZK Shell/Cli re-executes last command on exit
> ---------------------------------------------
>
>                 Key: ZOOKEEPER-1535
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1535
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: scripts
>         Environment: zookeeper-3.4.3 release
>            Reporter: Stu Hood
>            Assignee: Edward Ribeiro
>              Labels: cli, shell, zkcli, zkcli.sh
>         Attachments: ZOOKEEPER-1535-1.patch, ZOOKEEPER-1535-2.patch
>
>
> In the ZK 3.4.3 release's version of zkCli.sh, the last command that was 
> executed is *re*-executed when you {{ctrl+d}} out of the shell. In the 
> snippet below, {{ls}} is executed, and then {{ctrl+d}} is triggered (inserted 
> below to illustrate), the output from {{ls}} appears again, due to the 
> command being re-run. 
> {noformat}
> [zk: zookeeper.example.com:2181(CONNECTED) 0] ls /blah
> [foo]
> [zk: zookeeper.example.com:2181(CONNECTED) 1] <ctrl+d> [foo]
> $
> {noformat}

--
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

Reply via email to