On Thu, Mar 16, 2017 at 3:51 PM, Thomas Costigliola <[email protected]> wrote: > I just tested on a local drive and it does not seem to have the same > problem. So I guess the new question is, is there a fix for network drives?
Offhand I'm not sure. Why type of network drive is it? Do the timestamps get updated even if you run cl manually outside of tup? (ie: run cl and check the timestamp of the output, then wait a few seconds and check again to see if it changes). You might want to use something that gives you the full resolution of timestamps - internally tup uses the buf.st_mtime field on Windows from a stat call. Maybe there's some type of sync command we can run to force the timestamp to be updated after the file is closed. -Mike -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
