Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 19 Oct 2005 08:35:01 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Timestamp not preserved by Cygwin sshd Message-ID: <20051019063501.GA9127@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20051019042058 DOT 43539 DOT qmail AT web52510 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051019042058.43539.qmail@web52510.mail.yahoo.com> User-Agent: Mutt/1.4.2i 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/