Thanks everyone who replied. You know, I was a bit apprehensive about posting originally, because I had heard the git ML was inflammable. But all these responses have been prompt, well-thought-out and informative. I plan to take all these suggestions and have a go at hacking a race-free index which updates successfully despite concurrent file operations. Thanks again, -Ben On Wed, Jun 11, 2008 at 5:46 AM, Stephen R. van den Berg <srb@xxxxxxx> wrote: > Ben Lynn wrote: >>That is problematic. How do I figure out what the filesystem thinks is >>the current time? I could touch some file and read its mtime, but I >>want a shortcut. > > That basically is as short as it gets, except perhaps statting a freshly > modified file (not necessarily by oneself). > >>Are there any guarantees of any kind? e.g. is the filesystem current >>time at least never ahead of the system time? > > Practically no guarantees, just that it is rather likely for the time at > the fileserver to progress at about the same pace as yours. > -- > Sincerely, > Stephen R. van den Berg. > > Differentiation is an integral part of calculus. > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
