> 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.
>
Hi, thanks for the response. I apologize for not
supplying a test case. Here's a modification of your
example program that demonstrates what I mean:
#include <utime.h>
#include <sys/stat.h>
#include <sys/types.h>
int main()
{
struct utimbuf s;
struct utimbuf s2;
struct stat info;
s.actime = 0;
s.modtime = 1;
utime ("./x", &s);
stat("./x",&info);
printf(" utime.file access time is %ld\n",
info.st_atime); // prints "1". I would expect "0".
s.actime = 3;
s.modtime = 1;
utime ("./x", &s);
stat("./x",&info);
printf(" utime.file access time is %ld\n",
info.st_atime); // prints "3", which is both expected
and inconsistent with the one above.
}
I'm on cygwin-1.3.5 and Windows2000
Thanks,
Chad
__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
--
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/
