X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: File creation time oddity Date: Thu, 16 Aug 2007 21:53:39 +0000 (UTC) Lines: 24 Message-ID: References: <387E9FC1619C0849BA8934938037E54F0F5E29 AT sv-muc-004 DOT venyon-mail DOT local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 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 your system clock and BIOS clock match? Have you recently used an NTP server to align your clock with the rest of the world? However, I want one thing to be clear - ls does not list creation time; it lists change time (ctime not stand for creation time in POSIX, instead, the BSD notion birthtime, aka Btime, maps to the Windows creation time - for full birthtime support in cygwin, you need to use a snapshot, as cygwin 1.5.24 does not support querying birthtime). Also, stat(1) may be nicer than ls(1) for figuring these timestamp issues out. -- Eric Blake volunteer cygwin coreutils maintainer -- 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/