> > So the effect seems to be the same as before: As if a
> different clock
> > were used when calculating the time stamps for creating a file, or
> > for modifying it.
>
> Hmm, could it be that your files reside on a remote mount,
> and that NFS is
> reflecting the time of the remote machine (i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Redirecting to the list - http://cygwin.com/acronyms/#PPIOSPE
According to Ronald Fischer on 8/17/2007 1:46 AM:
>>> ~/thome/tmp $ date
>>> Thu Aug 16 16:49:35 2007
>>> ~/thome/tmp $ ls -l dummy3
>>> -rw-r--r-- 1 rfischer mkgroup-l-d 2 Aug 16 16:42
Ronald Fischer venyon.com> writes:
> ~/thome/tmp $ date
> Thu Aug 16 16:49:35 2007
> ~/thome/tmp $ ls -l dummy3
> -rw-r--r-- 1 rfischer mkgroup-l-d 2 Aug 16 16:42 dummy3
>
> As you can see, ls -l shows 16:42 for the creation time,
No idea why your ctime and mtime disagree - are you sure you
On my system, the initial (creation) time for a file
seems to be around 7 minutes shifted to the past.
This is reproducible:
~/thome/tmp $ date
Thu Aug 16 16:49:18 2007
~/thome/tmp $ ls -l dummy3
ls: cannot access dummy3: No such file or directory
~/thome/tmp $ echo x >dummy3
~/thome/tmp $ dat
4 matches
Mail list logo