X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 8 Oct 2009 15:11:03 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: atime on symlinks Message-ID: <20091008131103.GF12789@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4ACDD5C2 DOT 9010104 AT byu DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ACDD5C2.9010104@byu.net> User-Agent: Mutt/1.5.17 (2007-11-01) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Oct 8 06:06, Eric Blake wrote: > I've been trying to use lutimes and utimensat(,AT_SYMLINK_NOFOLLOW) to > play with symlink timestamps. mtime can be modified just fine, but atime > changes are lost the moment you lstat() the symlink again (probably > because path.cc opens the symlink file during path resolution to read its > contents and confirm it is a symlink). POSIX states that readlink() > changes the atime of a symlink, but not lstat(). Is there a way to make > path.cc resolution behave as if O_NOATIME were in effect for symlink > resolution, so that lstat() and path resolution leaves symlink times > alone, and only an explicit readlink() or lutimes() will adjust atime on > symlinks? I'm not aware that Windows supports a file open flag similar to the O_NOATIME flag. That would require to store and restore the atime every time a symlink is read, and we must read the symlink content to fetch the correct filesize. Are you still testing on XP? AFAIK, starting with Vista, filesystems are by default running in a noatime mount mode anyway. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple