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
Date: Tue, 12 Apr 2005 14:15:21 +0100
From: thomas DOT revell AT powerconv DOT alstom DOT com
Subject: Re: ctime updated unexpectedly
To: cygwin AT cygwin DOT com
Cc: Eric Blake <ebb9 AT byu DOT net>
Message-id: <OF8EDB7752.B7087560-ON80256FE1.004885DA-80256FE1.0049729C@test.alstom.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-IsSubscribed: yes

> OK, thanks for the advice. Do you know if there is any way I can get the 

> information I was expecting. If not, I'll have to make some major 
changes 
> to some complicated shell scripts :(

Sorry, I don't know of any way with POSIX semantics to track when just
file metadata has changed.  There are several utilities such as cmp,
md5sum, diff, etc. that can tell you if files have the same contents.  You
might try asking on a Unix users newsgroup, since it is not just cygwin
that has the property of file modifications touching both ctime and mtime.

Fair enough. The changes weren't actually as bad as I expected. Thanks 
again for your advice.

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