[deployment-guide/comm-rel: 22/41] Updated the Using the scp Utility section.
dsilas
dsilas at fedoraproject.org
Fri Jul 16 08:53:43 UTC 2010
commit 7db6f50d6e3f7778b3737aba091c56cdfa935f98
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Tue Jul 13 18:34:57 2010 +0200
Updated the Using the scp Utility section.
en-US/OpenSSH.xml | 49 ++++++++++++++++++++++++++-----------------------
1 files changed, 26 insertions(+), 23 deletions(-)
---
diff --git a/en-US/OpenSSH.xml b/en-US/OpenSSH.xml
index 0f973b7..f07768e 100644
--- a/en-US/OpenSSH.xml
+++ b/en-US/OpenSSH.xml
@@ -580,7 +580,7 @@ It is also possible that the RSA host key has just been changed.</screen>
<command>ssh</command> allows you to log in to a remote machine and execute commands there. It is a secure replacement for the <command>rlogin</command>, <command>rsh</command>, and <command>telnet</command> programs.
</para>
<para>
- Similarly to <command>telnet</command>, to log in to a remote machine named <systemitem class="domainname">penguin.example.net</systemitem>, type the following command at a shell prompt:
+ Similarly to <command>telnet</command>, to log in to a remote machine named <systemitem class="domainname">penguin.example.com</systemitem>, type the following command at a shell prompt:
</para>
<screen>~]$ <command>ssh penguin.example.com</command></screen>
<para>
@@ -596,8 +596,8 @@ Are you sure you want to continue connecting (yes/no)?</screen>
<para>
Type <userinput>yes</userinput> to confirm. You will see a notice that the server has been added to the list of known hosts, and a prompt asking for your password:
</para>
- <screen>Warning: Permanently added 'penguin.example.net' (RSA) to the list of known hosts.
-john at penguin.example.net's password:</screen>
+ <screen>Warning: Permanently added 'penguin.example.com' (RSA) to the list of known hosts.
+john at penguin.example.com's password:</screen>
<important>
<title>Important</title>
<para>
@@ -608,7 +608,7 @@ john at penguin.example.net's password:</screen>
After entering the password, you will be provided with a shell prompt for the remote machine.
</para>
<para>
- Alternatively, the <command>ssh</command> program can be used to execute a command on the remote machine without logging in to a shell prompt. The syntax for that is <command>ssh [<replaceable>username</replaceable>@]<replaceable>hostname</replaceable> <replaceable>command</replaceable></command>. For example, if you want to execute the command <command>whoami</command> on <systemitem class="domainname">penguin.example.com</systemitem>, type:
+ Alternatively, the <command>ssh</command> program can be used to execute a command on the remote machine without logging in to a shell prompt. The syntax for that is <command>ssh [<replaceable>username</replaceable>@]<replaceable>hostname</replaceable> <replaceable>command</replaceable></command>. For example, if you want to execute the <command>whoami</command> command on <systemitem class="domainname">penguin.example.com</systemitem>, type:
</para>
<screen>~]$ <command>ssh john at penguin.example.com whoami</command>
john at penguin.example.com's password:
@@ -617,8 +617,8 @@ john</screen>
After you enter the correct password, the username will be displayed, and you will return to your local shell prompt.
</para>
</section>
- <section id="s2-openssh-using-scp">
- <title>Using the <command>scp</command> Command</title>
+ <section id="s2-ssh-clients-scp">
+ <title>Using the <command>scp</command> Utility</title>
<indexterm>
<primary>
<command>scp</command>
@@ -638,33 +638,36 @@ john</screen>
</primary>
</indexterm>
<para>
- The <command>scp</command> command can be used to transfer files between machines over a secure, encrypted connection. It is similar to <command>rcp</command>.
+ <command>scp</command> can be used to transfer files between machines over a secure, encrypted connection. In its design, it is very similar to <command>rcp</command>.
</para>
<para>
- The general syntax to transfer a local file to a remote system is as follows:
+ To transfer a local file to a remote system, use the command in the following form:
</para>
- <screen>scp <replaceable><localfile></replaceable> <replaceable>username at tohostname:<remotefile></replaceable></screen>
+ <screen><command>scp <replaceable>localfile</replaceable> <replaceable>username</replaceable>@<replaceable>hostname</replaceable>:<replaceable>remotefile</replaceable></command></screen>
<para>
- The <replaceable><localfile></replaceable> specifies the source including path to the file, such as <filename>/var/log/maillog</filename>. The <replaceable><remotefile></replaceable> specifies the destination, which can be a new filename such as <filename>/tmp/hostname-maillog</filename>. For the remote system, if you do not have a preceding <command>/</command>, the path will be relative to the home directory of <replaceable>username</replaceable>, typically <filename>/home/username/</filename>.
+ For example, if you want to transfer <filename>taglist.vim</filename> to a remote machine named <systemitem class="domainname">penguin.example.com</systemitem>, type the following at a shell prompt:
</para>
+ <screen>~]$ <command>scp taglist.vim john at penguin.example.com:.vim/plugin/taglist.vim</command>
+john at penguin.example.com's password:
+taglist.vim 100% 144KB 144.5KB/s 00:00</screen>
<para>
- To transfer the local file <filename>shadowman</filename> to the home directory of your account on penguin.example.net, type the following at a shell prompt (replace <replaceable>username</replaceable> with your username):
- </para>
- <screen>scp shadowman <replaceable>username</replaceable>@penguin.example.net:shadowman</screen>
- <para>
- This will transfer the local file <filename>shadowman</filename> to <filename>/home/<replaceable>username</replaceable>/shadowman</filename> on penguin.example.net. Alternately, you can leave off the final <computeroutput>shadowman</computeroutput> in the <command>scp</command> command.
- </para>
+ Multiple files can be specified at once. To transfer the contents of <filename>.vim/plugin/</filename> to the same directory on the remote machine <systemitem class="domainname">penguin.example.com</systemitem>, type the following command:
+ </para>
+ <screen>~]$ <command>scp .vim/plugin/* john at penguin.example.com:.vim/plugin/</command>
+john at penguin.example.com's password:
+closetag.vim 100% 13KB 12.6KB/s 00:00
+snippetsEmu.vim 100% 33KB 33.1KB/s 00:00
+taglist.vim 100% 144KB 144.5KB/s 00:00</screen>
<para>
- The general syntax to transfer a remote file to the local system is as follows:
+ To transfer a remote file to the local system, use the following syntax:
</para>
- <screen>scp <replaceable>username at tohostname:<remotefile></replaceable> <replaceable><newlocalfile></replaceable></screen>
+ <screen><command>scp <replaceable>username</replaceable>@<replaceable>hostname</replaceable>:<replaceable>remotefile</replaceable> <replaceable>localfile</replaceable></command></screen>
<para>
- The <replaceable><remotefile></replaceable> specifies the source including path, and <replaceable><newlocalfile></replaceable> specifies the destination including path.
+ For instance, to download the <filename>.vimrc</filename> configuration file from the remote machine, type:
</para>
- <para>
- Multiple files can be specified as the source files. For example, to transfer the contents of the directory <filename>downloads/</filename> to an existing directory called <filename>uploads/</filename> on the remote machine penguin.example.net, type the following at a shell prompt:
- </para>
- <screen>scp downloads/* <replaceable>username</replaceable>@penguin.example.net:uploads/</screen>
+ <screen>~]$ <command>scp john at penguin.example.com:.vimrc .vimrc</command>
+john at penguin.example.com's password:
+.vimrc 100% 2233 2.2KB/s 00:00</screen>
</section>
<section id="s2-openssh-using-sftp">
<title>Using the <command>sftp</command> Command</title>
More information about the docs-commits
mailing list