Re: scp kopiert nicht

On Fri, Feb 06, 2004 at 11:28:30AM +0100, Marian Hettwer wrote:
>
> -- snip --
>
> debug1: channel 0: open confirm rwindow 0 rmax 32768
> This fortune brought to you by:
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ich würde mal versuchen das shell prompt
und den fortune-Aufruf entweder mit einem

% if ($?prompt) then
% endif

kapseln oder (besser?) in
die ~/.login verlegen.

Hier bekommt nämlich (soweit ich das
beurteilen kann) scp die Ausgabe von deinem
login-skript mit.

Was mich allerdings wundert ist, daß das nicht
erkannt wird. Zum Vergleich:

peter(at)abraxis ~% cat ~/.zshenv
export PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/opt/bin:/usr/games:/sbin:/usr/sbin:/usr/local/sbin:/opt/sbin
fortune

peter(at)abraxis ~% scp -v abraxis:~/test /dev/null
Office Automation, n.:
        The use of computers to improve efficiency by removing anyone
        you would want to talk with over coffee.
Executing: program /opt/openssh-3.7.1p2/bin/ssh host abraxis, user (unspecified), command scp -v -r -f ~/test
OpenSSH_3.7.1p2, SSH protocols 1.5/2.0, OpenSSL 0.9.7-beta3 30 Jul 2002
debug1: Reading configuration data /home/peter/.ssh/config
debug1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to abraxis [192.168.23.1] port 22.
debug1: Connection established.
debug1: identity file /home/peter/.ssh/id_dsa type -1
debug1: identity file /home/peter/.ssh/id_rsa type 1
debug1: identity file /home/peter/.ssh/id_dsa type -1
debug1: identity file /home/peter/.ssh/id_rsa type 1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.7.1p2
debug1: match: OpenSSH_3.7.1p2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.7.1p2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes256-cbc hmac-ripemd160 none
debug1: kex: client->server aes256-cbc hmac-ripemd160 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'abraxis' is known and matches the RSA host key.
debug1: Found key in /home/peter/.ssh/known_hosts:4
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/peter/.ssh/id_dsa
debug1: Offering public key: /home/peter/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 533
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending command: scp -v -r -f ~/test
protocol error: mtime.sec not delimited
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: fd 2 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 1

Gibt sinnvollerweise Fehler.

Wenn in deiner ~/.cshrc nichts persönliches drinsteht,
kannst du sie ja eventuell mal hier verbreiten, vielleicht
lassen sich daraus Schlüsse ziehen :-).

Grüße zurück,
  Peter

To Unsubscribe: send mail to majordomo(at)de.FreeBSD.org
with "unsubscribe de-bsd-questions" in the body of the message
Received on Sat 07 Feb 2004 - 09:22:37 CET