From 182c7b954620e9287ba2ddce9b1cbaceb1bddbaf Mon Sep 17 00:00:00 2001
From: Hans Nilsson
Date: Thu, 21 Jun 2018 10:38:51 +0200
Subject: ssh: Bug fix sftp error codes
Report the signal name if the signal error message is ""
Do not report a return code of 0 as an error.
---
lib/ssh/doc/src/ssh_sftp.xml | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
(limited to 'lib/ssh/doc/src/ssh_sftp.xml')
diff --git a/lib/ssh/doc/src/ssh_sftp.xml b/lib/ssh/doc/src/ssh_sftp.xml
index 129426a6d5..f367560b5f 100644
--- a/lib/ssh/doc/src/ssh_sftp.xml
+++ b/lib/ssh/doc/src/ssh_sftp.xml
@@ -46,9 +46,9 @@
reason()
-
-
= atom() A description of the reason why an operation failed.
+ = atom() | string() | tuple() A description of the reason why an operation failed.
- The value is formed from the sftp error codes in the protocol-level responses as defined in
+ The atom() value is formed from the sftp error codes in the protocol-level responses as defined in
draft-ietf-secsh-filexfer-13.txt
section 9.1.
@@ -57,6 +57,10 @@
E.g. the error code SSH_FX_NO_SUCH_FILE
will cause the reason() to be no_such_file.
+ The string() reason is the error information from the server in case of an exit-signal. If that information is empty, the reason is the exit signal name.
+
+ The tuple() reason are other errors like the {exit_status,integer()} if the exit status is not 0.
+
ssh_connection_ref() =
--
cgit v1.2.3