File creation time?

This is a multipart message in MIME format.
--===============0784116337==
Content-Type: multipart/alternative;
boundary="=_alternative 005CFEE88625723D_="

This is a multipart message in MIME format.
--=_alternative 005CFEE88625723D_=
Content-Type: text/plain; charset="us-ascii"

Gurus,

Is there any way to get the creation time of a file? I looked at -C and
the ctime returned by a stat() call, but those both give the file's "inode
change time," whatever that means. Second question: what *does* that
mean? The camel doesn't say.

TIA

Deane Rothenmaier
Systems Architect
Walgreens Corp.
847-914-5150

"In theory there is no difference between theory and practice. In practice
there is." -- Yogi Berra
--=_alternative 005CFEE88625723D_=
Content-Type: text/html; charset="us-ascii"



Gurus,



Is there any way to get the creation time of a file?  I looked at -C and the ctime returned by a stat() call, but those both give the file's "inode change time," whatever that means.  Second question: what *does* that mean? The camel doesn't say.



TIA



Deane Rothenmaier

Systems Architect

Walgreens Corp.

847-914-5150



"In theory there is no difference between theory and practice. In practice there is." -- Yogi Berra
--=_alternative 005CFEE88625723D_=--


--===============0784116337==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============0784116337==--

Re: File creation time?

Deane.Rothenmaier@walgreens.com wrote:

>
> Gurus,
>
> Is there any way to get the creation time of a file? I looked at -C and
> the ctime returned by a stat() call, but those both give the file's
> "inode change time," whatever that means. Second question: what *does*
> that mean? The camel doesn't say.

What OS ? ctime should be OK on Windoze, atime not so sure.

One explanation of ctime/"inode change time":

"The inode change time represents the time when the file's meta-information last
changed. One common example of this is when the permissions of a file change.
Changing the permissions doesn't access the file, so the atime doesn't change,
nor does it modify the file, so the mtime doesn't change. Yet, something about
the file itself has changed, and this must be noted somewhere. This is the job
of the ctime field. This is necessary, so that, for example, a backup program
can make a fresh copy of the file, including the new permissions value.
Another operation that modifies a file's ctime without affecting the others is
renaming. In any case, it is not possible, in normal operations, for a user to
change the ctime field to a user-specified value."
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

RE: File creation time?

$Bill Luebkert <> wrote:
> Deane.Rothenmaier@walgreens.com wrote:
>
>>
>> Gurus,
>>
>> Is there any way to get the creation time of a file? I looked at -C
>> and the ctime returned by a stat() call, but those both give the
>> file's "inode change time," whatever that means. Second question:
>> what *does* that mean? The camel doesn't say.
>
> What OS ? ctime should be OK on Windoze, atime not so sure.
>
> One explanation of ctime/"inode change time":
>
> "The inode change time represents the time when the file's
> meta-information last changed. One common example of this is when
> the permissions of a file change.
> Changing the permissions doesn't access the file, so the atime
> doesn't change, nor does it modify the file, so the mtime doesn't
> change. Yet, something about the file itself has changed, and this
> must be noted somewhere. This is the job of the ctime field. This
> is necessary, so that, for example, a backup program can make a fresh
> copy of the file, including the new permissions value. Another
> operation that modifies a file's ctime without affecting the others
> is renaming. In any case, it is not possible, in normal operations,
> for a user to change the ctime field to a user-specified value."

That seems like quite a good description, without getting into the
implementation details of a *nix file system. Can you cite the source
for your quote, or would you have to kill all of the list subscribers
:-) ?

--
Brian Raven

_________________________________________

The information contained in this e-mail is confidential and solely
for the intended addressee(s). Unauthorised reproduction, disclosure,
modification, and/or distribution of this email may be unlawful. If you
have received this email in error, please notify the sender immediately
and delete it from your system. The views expressed in this message
do not necessarily reflect those of Atos Euronext Market Solutions.
_________________________________________



=================================
Atos Euronext Market Solutions Disclaimer
=================================
The information contained in this e-mail is confidential and solely for the intended addressee(s). Unauthorised reproduction, disclosure, modification, and/or distribution of this email may be unlawful.
If you have received this email in error, please notify the sender immediately and delete it from your system. The views expressed in this message do not necessarily reflect those of Atos Euronext Market Solutions.

L'information contenue dans cet e-mail est confidentielle et uniquement destinee a la (aux) personnes a laquelle (auxquelle(s)) elle est adressee. Toute copie, publication ou diffusion de cet email est interdite. Si cet e-mail vous parvient par erreur, nous vous prions de bien vouloir prevenir l'expediteur immediatement et d'effacer le e-mail et annexes jointes de votre systeme. Le contenu de ce message electronique ne represente pas necessairement la position ou le point de vue d'Atos Euronext Market Solutions.

_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Re: File creation time?

Brian Raven wrote:

> That seems like quite a good description, without getting into the
> implementation details of a *nix file system. Can you cite the source
> for your quote, or would you have to kill all of the list subscribers
> :-) ?

Google is my friend: http://www.delorie.com/gnu/docs/textutils/coreutils_82.html
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Re: File creation time?

I've always wondered why Unix doesn't have a file creation time...

$Bill Luebkert wrote:
> Brian Raven wrote:
>
>> That seems like quite a good description, without getting into the
>> implementation details of a *nix file system. Can you cite the source
>> for your quote, or would you have to kill all of the list subscribers
>> :-) ?
>
> Google is my friend: http://www.delorie.com/gnu/docs/textutils/coreutils_82.html
> _______________________________________________
> ActivePerl mailing list
> ActivePerl@listserv.ActiveState.com
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
>
>


--

I always have coffee when I watch radar!
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs