delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/10/19/05:32:17

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <20051019093201.89283.qmail@web52512.mail.yahoo.com>
Date: Wed, 19 Oct 2005 02:32:01 -0700 (PDT)
From: Alex Luso <tapadamocho AT yahoo DOT com>
Subject: Re: Timestamp not preserved by Cygwin sshd
To: cygwin AT cygwin DOT com
In-Reply-To: <20051019063501.GA9127@calimero.vinschen.de>
MIME-Version: 1.0
X-IsSubscribed: yes

  Perhaps you are right and it doesn't have to do with
cygwin. I found this to happen when I tried to scp to
cygwin with two different clients from 2 different
machines (both non-OpenSSH, I believe). On the other
hand, when I scp in between these 2 clients, there was
no error. So I suppose this is an incompatibility
between different flavors of SSH?
  Can someone suggest a workaround - i.e. settings on
the server side (cygwin/OpenSSH) - that would resolve
the failure of the -p switch from a non-OpenSSH
client? I am using a nice gui for SCPing files between
windows machines (SSH Secure Shell 3.2) and would like
to be able to continue to use it.

  Thanks for any help.
  -Alex

--- Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
wrote:

> On Oct 18 21:20, Alex Luso wrote:
> > 
> >   Hi,
> >  
> >   I just noticed a bug in Cygwin ssd.
> > 
> >   If I try to preserve the time stamp of a file
> that I
> > transfer via scp to a XP machine running Cygwin's
> > sshd, the file gets copied but the timestamp is
> not
> > preserved.
> > 
> >   The specific error that is reported is:
> > ------
> > scp: warning: File transfer protocol mismatch.
> > scp: FATAL: sshfc_transfer.c:2496 SshFCTransfer
> > (function name unavailable) Unreachable code
> failed:
> > Invalid code reached.
> > ------
> 
> This is an error message of a non-OpenSSH scp
> client.  OpenSSH's
> ssh is usually working fine, also in setting
> timestamps when copying
> files, also on Cygwin.  This is very likely a
> problem between your
> other scp client and OpenSSH and has nothing to do
> with Cygwin.
> 
> 
> Corinna
> 
> -- 
> Corinna Vinschen                  Please, send mails
> regarding Cygwin to
> Cygwin Project Co-Leader          cygwin AT cygwin
> DOT com
> Red Hat, Inc.
> 
> --
> Unsubscribe info:     
> http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:      
> http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019