mmhh... could be my memory plays tricks on me, but what brought me to thinking that the mtime/epoch isn't timezone corrected were a number of stats() where the time was skewed against what Windows or the CLI stat told me.
Now thinking again, I tend to accept stat() returns GMT epoch.
Still, are you sure this is consistent across *nix and Windows. Does a Perl stat() on Windows/NTFS return GMT epoch - really?
The incident where I ran into this skew, if I recall correctly, was a script that worked across filesystems (although both NTFS). It recorded the stat() on a file on a first filesystem and then duplicated the file and its stat() on a second. When I looked at the cloned file's metadata via Windows's file properties it showed a 1 hour time offset. And I couldn't quite figure out if this bug was introduced by my script, by Windows/NTFS or an ignorance of the TZ offset in stat(). stat() returning time-zone-offset'ed epochs would have beautifully explained it...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.