On Thu, Sep 27, 2012 at 09:37:59AM +0100, Richard Shann wrote: > On Wed, 2012-09-26 at 14:56 -0600, Josue Abarca wrote: > > On Wed, Sep 26, 2012 at 06:46:16PM +0100, Richard Shann wrote: ... > > st_mtim.tv_nsec <- to see the nano seconds. > > > > (of course the file system must support nanoseconds time stamps) > Thanks - it seems I have been on the right track - I was looking at > tv_nsec in the debugger and it is always 0. IIRC Debian stable uses ext2 > filesystem - could it be that it doesn't record nano-second > timestamps?
Ext2 does not support, nano-second timestamps :(. Debian stable (squeeze) uses ext3 by default, but AFAIK time nano-second timestamps were introduced in ext4 [0]. Debian stable also supports ext4, but you need to select the option in the partitioning step (I always choose ext4 :P). > Even if it didn't have the precision to give accurate information it > could always increment tv_nsec by 1 every time it modified a file with > the same value of tv_sec. > If this is really the situation I guess I should find another way - I > need to do something for the Windows system anyway as that doesn't do > file locking the same way as unix. So I will maybe need to keep changing > the filename that LilyPond stores to, though it is nice to keep the old > one for viewing... > > Richard Maybe inotify could be used, but this would be only for GNU/Linux, so I guess that maybe changing the file name is a better approach. [0] http://en.wikipedia.org/wiki/Ext4 [1] https://www.ibm.com/developerworks/linux/library/l-inotify/ -- Josué M. Abarca S. Vos mereces Software Libre. PGP key 4096R/70D8FB2A 2009-06-17 Huella de clave = B3ED 4984 F65A 9AE0 6511 DAF4 756B EB4B 70D8 FB2A _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
