Subject: Re: 1.5.5.1 st_ctime and st_mtime is not updated for functions.
From: Gregory Borota <[email-masked]>
Cc: [email-masked]
Date: Fri, 5 Mar 2004 03:57:39 -0600

Forgive my ignorance just wondering what does PERROR has to do with
st_ctime and st_mtime. You mean when you redirect stderr to a file?

Greg

On Fri, 5 Mar 2004, Vinay Kumar wrote:

> Hi all,
>    I ran PCTS on cygwin 1.5.5.1 and found some problem. According to
> standard document of posix conformance  following function need to update
> the st_ctime and st_mtime fields of the underlying file. These functions
> are not doing so. Is there any specific reason for that? Is it
> implementation limitation or a design contraint?
>
> fclose(11A), fflush(04A), fputc(04A), fputs(04A),freopen(26A,27A), fseek(11A),
> perror(04A), printf(11A), fprintf(11A), vprintf(11A), vfprintf(12A), putc(11A), puts(11A), remove(18A),
> rewind(4A), creat(37A,38A), link(39A), unlink(25A),rmdir(23A),
> rename(43A), stat(29A), fstat(13A), chmod(24A),  utime(25A).
>
> Functions written above are failing in updating the st_ctime and st_mtime
> fields of the underlying, which is a basic assertion according to POSIX.1.
> The example of one assertion is below
>            11A -  When the stream is writable and buffered data is caused
> to be written, then a call to fclose(stream) marks for update the st_ctime
> and st_mtime fields of the underlying file.
>
> Any help in this regard is appreciated.
>
>
> regards
> Vinay
>
> Note: fclose(11A) means Assertion number 11 for function "fclose" in
> standard document "IEEE std 2003.1-1992 Test Methods for Measuring
> Conformance to Posix-Part1 System Interface"
>
>
>
> --
> 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/
>
>

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