X-Spam-Check-By:	sourceware.org
From:	ericblake AT comcast DOT net (Eric Blake)
To:	"Paul J. Lucas" <pauljlucas AT mac DOT com>, cygwin AT cygwin DOT com
Subject:	Re: stat(2) of a directory
Date:	Sun, 05 Mar 2006 02:45:55 +0000
Message-Id:	<030520060245.29893.440A50E3000BB933000074C522007507440A050E040D0C079D0A@comcast.net>
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

> 	Under *nix, I can use stat(2) of a directory to know when its
> 	contents have changed (file added or deleted from it).
> 
> 	Under cygwin, this doesn't work because a directory's
> 	modification time doesn't change when its contents change.
> 
> 	Any recommendations as to how to monitor a directory to know
> 	when its contents change under cygwin?

On Win9x, this is basically impossible, since Windows does not
provide that capability (try it - touch . is a noop on cygwin on
Win9x).  On Windows NT, the capability exists, but since
Windows itself is not doing the timestamp update, it would
severely slow cygwin down to open the directory and touch the
directory's timestamp on every open or unlink, just to implement
this requirement of POSIX/SUSv3 properly.  It has been suggested
in the past that perhaps a 'CYGWIN=posixly_correct' option
be added that does all these slower corner cases, but no one
has bothered to implement it.

-- 
Eric Blake

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

- Raw text -