David Korn wrote: > > solaris file timestamps are of better-than sub-second resolution; these > > higher-resolution timestamps can be displayed with ls -E, but they are > > not included in the comparisons done by test's -nt and -ot operators. > > > > Filing as defect rather than RFE because the documentation for "test" > > makes no reference to any limited resolution of the timestamp but merely > > refers to whether the file is older or newer. > > > > this appears to be common across multiple shells (ksh, zsh, bash, > > /bin/test); I'm filing against ksh first to raise awareness of this. > > > > as systems speed up, the chance that scripts using -nt and -ot will > > break due to same-second timestamps increases. > > -- snip -- > > > > The question is: What is the correct behaviour in this case ? And how > > does ksh93r+ currently behave ? > > The complete ast toolkit was updated to handle subsecond time stamps > last year and -ot and -nt should work as well as other command > like nmake and touch which use fine granularity time stamps.
Ok... thanks for the info... :-) April: I think this may be an item for the ARC case - AFAIK the old Solaris ksh only compares the normal timestamps (e.g. up to 1sec resolution as described in http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6417347) ... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
