You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
libssh exit_status is only set by the exit-status packet/request, which is only sent for regular process exits. If the remote process exits due to a signal, an exit-signal request is sent instead, which doesn't set exit-status (which then remains at -1).
I'm halfway between
"this kinda sounds like a libssh bug, ssh_channel_get_exit_status should return the standard unixy composite, like wait(2) does"
and
"I guess we have to add a default callback for this and add a separate Channel.get_exit_signal function."
The text was updated successfully, but these errors were encountered:
libssh exit_status is only set by the
exit-status
packet/request, which is only sent for regular process exits. If the remote process exits due to a signal, anexit-signal
request is sent instead, which doesn't setexit-status
(which then remains at -1).I'm halfway between
"this kinda sounds like a libssh bug, ssh_channel_get_exit_status should return the standard unixy composite, like wait(2) does"
and
"I guess we have to add a default callback for this and add a separate Channel.get_exit_signal function."
The text was updated successfully, but these errors were encountered: