aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
author√Čric Bischoff <eric@bureau-cornavin.com>2010-09-06 11:03:00 +0200
committerAndreas Schneider <asn@cynapses.org>2010-09-06 11:03:00 +0200
commit38421403d2dc45636e597f2a909daa6ae31976de (patch)
tree3947257bc113d19d2af2e20b3d385af5c4a735ba /doc
parent461dde231c73fbe7daecc703a79fb1317bdd1b53 (diff)
downloadlibssh-38421403d2dc45636e597f2a909daa6ae31976de.tar.gz
libssh-38421403d2dc45636e597f2a909daa6ae31976de.tar.xz
libssh-38421403d2dc45636e597f2a909daa6ae31976de.zip
doc: Some corrections for shell execution.
Diffstat (limited to 'doc')
-rw-r--r--doc/commands.dox12
1 files changed, 10 insertions, 2 deletions
diff --git a/doc/commands.dox b/doc/commands.dox
index 1e52ed4a..86cf156b 100644
--- a/doc/commands.dox
+++ b/doc/commands.dox
@@ -6,6 +6,13 @@ Previous chapter has shown how to open a full shell session, with an attached
terminal or not. If you only need to execute commands on the remote end,
you don't need all that complexity.
+The method described here is suited for executing only one remote command.
+If you need to issue several commands in a row, you should consider using
+a non-interactive remote shell, as explained in previous chapter.
+
+@see shell
+
+
@subsection exec_remote Executing remote commands
The first steps for executing remote commands are identical to those
@@ -71,8 +78,9 @@ If an error has been encountered, it returns a negative value:
}
@endcode
-Once there are no more remote commands to execute, you can send an
-end-of-file to the channel, close it, and free the memory it used:
+Once you read the result of the remote command, you send an
+end-of-file to the channel, close it, and free the memory
+that it used:
@code
ssh_channel_send_eof(channel);