Earnie Boyd wrote:
> On Tue, Feb 28, 2012 at 3:24 PM, Frank Farance wrote:
>
>>
>> So I don't believe this is a WinSCP problem, AND the problem is
>> demonstrated independent of WinSCP.
>>
>
> What is TZ set to in your Cygwin environment? Try the string EST5EDT
> to see if it helps.
>
> --
> Earni
Corinna Vinschen wrote:
> On Feb 29 12:49, G.W. Haywood wrote:
>
>> Hi there,
>>
>>
>>> 175712 by: "Frank Farance"
>>> 175717 by: Corinna Vinschen
>>> 175719 by: "Frank Farance"
>>> 175720 by: Corinna Vinschen
>>> 175721 by: "Frank Farance"
>>> 175722 by: Corinna Vinschen
>>> 175725 by: Earnie Boyd
On Feb 29 12:49, G.W. Haywood wrote:
> Hi there,
>
> >175712 by: "Frank Farance"
> >175717 by: Corinna Vinschen
> >175719 by: "Frank Farance"
> >175720 by: Corinna Vinschen
> >175721 by: "Frank Farance"
> >175722 by: Corinna Vinschen
> >175725 by: Earnie Boyd
> >175728 by: "Frank Farance"
>
> Wha
On Tue, Feb 28, 2012 at 3:24 PM, Frank Farance wrote:
>
> So I don't believe this is a WinSCP problem, AND the problem is
> demonstrated independent of WinSCP.
>
What is TZ set to in your Cygwin environment? Try the string EST5EDT
to see if it helps.
--
Earnie
-- https://sites.google.com/site/e
Hi there,
175712 by: "Frank Farance"
175717 by: Corinna Vinschen
175719 by: "Frank Farance"
175720 by: Corinna Vinschen
175721 by: "Frank Farance"
175722 by: Corinna Vinschen
175725 by: Earnie Boyd
175728 by: "Frank Farance"
What are the filesystems involved? VFAT anywhere?
--
73,
Ged.
--
Earnie Boyd wrote:
> On Tue, Feb 28, 2012 at 1:20 PM, Corinna Vinschen wrote:
>
>>
>> I don't know. Â I can't see that anything's wrong with Cygwin here. Â I
>> just searched the web and found other people having timestamp problems
>> with WinSCP without any Cygwin involvement:
>>
>> Â http://win
On Tue, Feb 28, 2012 at 1:20 PM, Corinna Vinschen wrote:
>
> I don't know. I can't see that anything's wrong with Cygwin here. I
> just searched the web and found other people having timestamp problems
> with WinSCP without any Cygwin involvement:
>
> http://winscp.net/forum/viewtopic.php?t=8382
On Feb 28 12:23, Frank Farance wrote:
> > Not for me. The only difference I see is that I'm living in another
> > timezone. I changed my timezone to America/New_York as well, but the time
> > is still correct in ls. Without a reproducible scenario (which does not
> > involve non-system, non-Cygwi
> On Feb 28 11:19, Frank Farance wrote:
>
>> Corinna Vinschen wrote:
>>
Furthermore, ls reports the wrong time (via --full-time) as 11:46
-0400.
Yes, ls has the right timezone offset (it was summer time in NYC on
2005-09-01), but the time itself is wrong. Even when I precede th
On Feb 28 11:19, Frank Farance wrote:
> Corinna Vinschen wrote:
> >> Furthermore, ls reports the wrong time (via --full-time) as 11:46 -0400.
> >> Yes, ls has the right timezone offset (it was summer time in NYC on
> >> 2005-09-01), but the time itself is wrong. Even when I precede the
> >> comma
Corinna Vinschen wrote:
> On Feb 28 10:00, Frank Farance wrote:
>
>> I've had Cygwin running on a Windows XP workstation for years using
>> rsync as my primary backup tool for my data files. The workstation just
>> crashed with a hard drive failure, I've replaced the drive and so on.
>> Initially,
On Feb 28 10:00, Frank Farance wrote:
> I've had Cygwin running on a Windows XP workstation for years using rsync
> as my primary backup tool for my data files. The workstation just crashed
> with a hard drive failure, I've replaced the drive and so on. Initially,
> I was recovering most of the f
I've had Cygwin running on a Windows XP workstation for years using rsync
as my primary backup tool for my data files. The workstation just crashed
with a hard drive failure, I've replaced the drive and so on. Initially,
I was recovering most of the files with WinSCP (5.0.5) from the backup
serve
13 matches
Mail list logo
