delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/10/21/00:54:41

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: <20051021045416.68136.qmail@web52511.mail.yahoo.com>
Date: Thu, 20 Oct 2005 21:54:16 -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: <43563287.3000703@equate.dyndns.org>
MIME-Version: 1.0
X-IsSubscribed: yes

  Alright, so the simplest solution was indeed to
switch to WinSCP client which does indeed preserve the
timestamp of the copied file correctly (and not a bad
GUI interface to boot). This resolved the
incompatibility between the -p switch from non-OpenSSH
clients and cygwin's OpenSSHD.

Thanks for the help Chris.
-Alex

P.S. Just as an aside - it turns out, however, that
now the timestamp of the folders are not preserved.
This is not a big deal but def. strange as the use of
non-OpenSSH clients preserved the folder's timestamp
(although not the files within). Odd, odd, but not a
big deal. I will direct the question to WinSCP as this
has likely nothing to do with cygwin. 

--- Chris Taylor <chris AT equate DOT dyndns DOT org> wrote:

> Alex Luso wrote:
> >   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.
> > 
> 
> Please don't top-post!
> 
> Anyway, a possible solution would be to use WinSCP -
> afaik this doesn't
> have any trouble preserving the timestamp. I know it
> doesn't with
> OpenSSH on debian, so I would assume this is also
> the case on cygwin -
> unfortunately I can't test this just now.
> It's also a very nice tool.. ;-)
> 
> 
> Chris
> 
> -- 
> 
> Spinning complacently in the darkness, covered and
> blinded by a blanket
> of little lives, false security has lulled the
> madness of this world
> into a slumber. Wake up! An eye is upon you, staring
> straight down and
> keenly through, seeing all that you are and
> everything that you will
> never be. Yes, an eye is upon you, an eye ready to
> blink. So face
> forward, with arms wide open and mind reeling. Your
> future has
> arrived... Are you ready to go?
> 
> --
> 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