Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <1109798389.42262df5e7c1d@webmail.namezero.com>
Date: Wed,  2 Mar 2005 13:19:49 -0800
From: eric AT melski DOT net
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
User-Agent: Internet Messaging Program (IMP) 3.2.3
Resent-Date: Wed,  2 Mar 2005 13:25:28 -0800
Resent-From: eric AT melski DOT net
Resent-To: cygwin AT cygwin DOT com
Resent-Message-ID: <1109798728 DOT 42262f483c919 AT webmail DOT namezero DOT com>
Subject: ctime: creation or change time?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit


I recently upgraded my Cygwin install to 1.5.13-1 from 1.5.12-1 and noticed that
cygwin is now setting the "ctime" for files after write operations.  I scanned
the list archives and saw the discussion of this change, but I saw no mention
of the fact that on Windows/NTFS, "ctime" is actually file creation time, not
file change time as it is on Unix.  I understand the motivation for wanting to
make Cygwin behave like POSIX, but in this instance it seems like that
compatibility has come at the cost of compatibility with Windows:  other
Windows applications will be "surprised" by the sudden change of the file
creation time when the file has not in fact been recreated.

In fact, NTFS has no notion of file change time as described in POSIX.  Is there
any chance of undoing this change?  An alternative solution might be to simply
use the NTFS file modify time for both the mtime and ctime of the file, since
those two are almost always updated together anyway.

Thanks,

Eric Melski


--
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/