Retourner au contenu associé (entrée de forum : Problème d'utilisation de scp)
Posté par Lol Zimmerli (site web personnel, Mastodon) le 26 janvier 2006 à 17:48. En réponse au message Problème d'utilisation de scp. Évalué à 2.
La gelée de coings est une chose à ne pas avaler de travers.
AltStyle によって変換されたページ (->オリジナル) / アドレス: モード: デフォルト 音声ブラウザ ルビ付き 配色反転 文字拡大 モバイル
# Quand ça marche...
Posté par Lol Zimmerli (site web personnel, Mastodon) . En réponse au message Problème d'utilisation de scp. Évalué à 2.
moi@babasse:/tmp/plop$ scp -rv USER@domaine.com:/tmp/* .
Executing: program /usr/bin/ssh host domaine.com, user USER, command scp -v -r -f /tmp/*
OpenSSH_4.2p1 Debian-5, OpenSSL 0.9.8a 11 Oct 2005
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to domaine.com [IP] port 22.
debug1: Connection established.
debug1: identity file /home/USER/.ssh/identity type 0
debug1: identity file /home/USER/.ssh/id_rsa type 1
debug1: identity file /home/USER/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.8.1p1 Debian-8.sarge.4
debug1: match: OpenSSH_3.8.1p1 Debian-8.sarge.4 pat OpenSSH_3.*
debug1: Local version string SSH-1.5-OpenSSH_4.2p1 Debian-5
debug1: Waiting for server public key.
debug1: Received server public key (768 bits) and host key (1024 bits).
debug1: Host 'domaine.com' is known and matches the RSA1 host key.
debug1: Found key in /home/USER/.ssh/known_hosts:1
debug1: Encryption type: 3des
debug1: Sent encrypted session key.
debug1: Installing crc compensation attack detector.
debug1: Received encrypted confirmation.
debug1: Trying RSA authentication via agent with 'moi@babasse'
debug1: Received RSA challenge from server.
debug1: Sending response to RSA challenge.
debug1: Remote: RSA authentication accepted.
debug1: RSA authentication accepted by server.
debug1: Requesting compression at level 6.
debug1: Enabling compression at level 6.
debug1: Sending command: scp -v -r -f /tmp/*
debug1: Entering interactive session.
debug1: fd 0 clearing O_NONBLOCK
Sending file modes: C0644 469 feed-icon-10x10.png
Sink: C0644 469 feed-icon-10x10.png
feed-icon-10x10.png 100% 469 0.5KB/s 00:00
Sending file modes: C0644 552 feed-icon-12x12.png
Sink: C0644 552 feed-icon-12x12.png
feed-icon-12x12.png 100% 552 0.5KB/s 00:00
Sending file modes: C0644 764 feed-icon-16x16.png
Sink: C0644 764 feed-icon-16x16.png
feed-icon-16x16.png 100% 764 0.8KB/s 00:00
Sending file modes: C0644 1090 feed-icon-24x24.png
Sink: C0644 1090 feed-icon-24x24.png
feed-icon-24x24.png 100% 1090 1.1KB/s 00:00
Sending file modes: C0644 1441 feed-icon-32x32.png
Sink: C0644 1441 feed-icon-32x32.png
feed-icon-32x32.png 100% 1441 1.4KB/s 00:00
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 11, stdout 4555, stderr 252 bytes in 0.8 seconds
debug1: Bytes per second: stdin 13.0, stdout 5374.6, stderr 297.3
debug1: Exit status 1
debug1: compress outgoing: raw data 91, compressed 80, factor 0.88
debug1: compress incoming: raw data 4892, compressed 4419, factor 0.90
C'est donc par là que ça te coince:
debug1: Sending command: scp -v -r -f /httpdocs/*
debug1: channel 0: request exec
La gelée de coings est une chose à ne pas avaler de travers.