Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 14 Nov 2001 21:13:34 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: utime Bug? Message-ID: <20011114211334.G27452@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com References: <20011114194337.46026.qmail@web13906.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011114194337.46026.qmail@web13906.mail.yahoo.com>; from chadfowler@yahoo.com on Wed, Nov 14, 2001 at 11:43:37AM -0800 On Wed, Nov 14, 2001 at 11:43:37AM -0800, chad fowler wrote: > I'm a new cygwin user and a fairly lame C programmer. > However, I think I've discovered a bug. When I find > things like this, I usually assume it's my fault. > But, this seems to be at least inconsistent with other > platforms. > > When you use utime to set the actime to 0 (the epoch), > stat will show actime as being whatever modtime is set > to for that file. If you set it to anything else (1, > for example), actime is reflected accurately by stat. > > Am I off base? The same code on my Debian box returns > the epoc for atime (instead of the modtime value). > > Does this make sense? Would you mind to create a small testcase? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/