On Thu, Sep 04, 2008 at 09:50:01AM -0700, chromatic wrote: > On Thursday 04 September 2008 01:19:44 Eric Wilhelm wrote: > > > Let's pretend that I'm a real jerk of an author and I only care about > > whether my code installs on a perl 5.8.8+ (a *real* perl -- no funky > > vendor patches) with a fully updated and properly configured toolchain > > and the clock set to within 0.65s of NTP time. > > Oh great, yet another check I have to add to my Build.PL. What's the magic > cantrip for THAT one? > > (Why yes, I *have* seen bugs related to time skew on network-mounted paths),
So have I. I think that there's at least one stat test in the core that will fail if you're testing on an NFS mount from a machine where the clock differs. IIRC it's because file creation time is stamped by the server, and file modification time is stamped with a time from the client, and if they're out the "impossible" can happen. Which when you're sanity testing the ops that read these sorts of things, you're looking out for. Although I suspect that there can be more general problems with make getting (correctly) confused by timestamps on files it touched. Nicholas Clark
