[
https://issues.apache.org/jira/browse/SSHD-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563347#comment-17563347
]
Lyor Goldstein commented on SSHD-1275:
--------------------------------------
As far as I can tell this behavior is consistent with the RFC (expected is a
value judgement...) - if the remote process dies before sending "exit-status"
packet or never sends it altogether then it is compliant - to quote [rfc4253
section-6.10|https://datatracker.ietf.org/doc/html/rfc4254#section-6.10]
{quote}
When the command running at the other end terminates, the following message can
be sent to return the exit status of the command. Returning the status is
RECOMMENDED.
{quote}
RECOMMENDED but not MANDATORY...
> Remote process is still available after
> ChannelExec.close(true).awaitUninterruptibly()
> --------------------------------------------------------------------------------------
>
> Key: SSHD-1275
> URL: https://issues.apache.org/jira/browse/SSHD-1275
> Project: MINA SSHD
> Issue Type: Question
> Affects Versions: 2.8.0
> Environment: Java SE 8, Apache NetBeans IDE 8.2
> Reporter: dgü
> Priority: Major
>
> Hello!
> If I close channel immediately by
> {{{}org.apache.sshd.client.channel.ChannelExec.close(true).awaitUninterruptibly(){}}},
> the remote process is not terminated and
> {{org.apache.sshd.client.channel.ChannelExec#getExitStatus()}} returns
> {{{}null{}}}.
> Even if I test with _Thread.sleep(60*1000)_ after channel close, the problem
> still happens. The problem doesn't happen when channel is closed gracefully.
> is this expected behaviour ?
>
> Thanks in advance!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
