Re: reply>> my first newbie question

Hi --

I believe that ctime is supposed to be change time, not creation time,
but there is confusion about this; you'll find textbooks that talk
about it as creation time, and others that talk about how that is a
misunderstanding.  I'm not sure what POSIX has to say about this, or
whether that matters, since obviously different platforms deal with it
differently.

Perhaps we can add a configure test that checks for this and use mtime
for platforms that give creation-time semantics for ctime.  I seem to
recall that there was a reason ctime was preferable to use than mtime,
but I've forgotten what it was.  Drew, do you remember our discussion
of this back in 2001?

js


On Wed, Nov 19, 2003 at 04:47:53PM +0100, Tomastiq wrote:
> Hi,
> 
> IMHO I've got it.
> As I see the problem is the ctime handling.
> In the (cygwin) documentation:
> "ctime = time of last modification of file status information"
> In python docs at stat() function:
> "st_ctime (time of most recent content modification or metadata change)"
> And skunk uses this ST_CTIME constant for checking the fresh of compiled
> version of html. But under cygwin this kind of date contains the
> creation date, so it is not changing. I think this is a win manner
> and cygwin uses this date. After I changed *_CTIME constants in files
> to *_MTIME everything is working fine. Hmm. Unfortunately I can't find
> information about this behaviour at cygwin.com.
> 
> thx.toma
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/u7MJuqamFyFXXLIRAupZAKDAO/5ixVAv2jvGocy/lo+Z0ZqPAwCdE8PZ
iILeJuWG7h3SJMoDlXQlj6o=
=T5TX
-----END PGP SIGNATURE-----