This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: utime Bug?
- From: egor duda <deo at logos-m dot ru>
- To: chad fowler <chadfowler at yahoo dot com>
- Cc: cygwin at cygwin dot com
- Date: Wed, 14 Nov 2001 23:14:00 +0300
- Subject: Re: utime Bug?
- Organization: deo
- References: <20011114194337.46026.qmail@web13906.mail.yahoo.com>
- Reply-to: egor duda <cygwin at cygwin dot com>
Hi!
Wednesday, 14 November, 2001 chad fowler chadfowler@yahoo.com wrote:
cf> When you use utime to set the actime to 0 (the epoch),
cf> stat will show actime as being whatever modtime is set
cf> to for that file. If you set it to anything else (1,
cf> for example), actime is reflected accurately by stat.
cf> Am I off base? The same code on my Debian box returns
cf> the epoc for atime (instead of the modtime value).
you should provide some details. a small testcase demonstrating a
problem is highly desirable. see http://cygwin.com/cygwin/bugs.html
for bug-reporting buidelines.
fwiw, this snippet:
#include <utime.h>
int main()
{
struct utimbuf s;
s.actime = s.modtime = 0;
return (utime ("./x", &s));
}
correctly sets access and modification times for file './x' with
cygwin-1.3.5 on windows nt 4.0
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
--
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/