Jarkko Hietaniemi <[EMAIL PROTECTED]> writes: >On Wed, Apr 03, 2002 at 05:37:00PM -0500, Michael G Schwern wrote: >> On Wed, Apr 03, 2002 at 11:37:21PM +0300, Jarkko Hietaniemi wrote: >> > NFS likely. I don't know what to do about this, detecting >> > that we are on NFS is ENONPORTABLE. >> >> Touch a file and see if it's mtime is significantly different than the >> current time? :) > >That gives you "we *might* be on NFS", when the situation might be >any of the "we are on working NFS" (oxymoron?), "we are on something >else broken", "your clock is broken", or something else...
I expect most people know this but ... Most of the time the mtime issue on NFS is because time returned is NFS server's idea of time. If that differs from clients idea of time you see weirdness. -- Nick Ing-Simmons http://www.ni-s.u-net.com/
