Re: Log length limit on Windows? Problem with using notepad as log editor?

On 3 Dec 2004 Ph. Marek wrote:

> And to make an informed guess regarding the original problem:
> 1) There's some documentation on microsoft (which I couldn't find ATM)
> regarding the granularity with which timestamps are updated on disk.
> I remember that being about 30 seconds or such like for FAT.

FAT timestamps have 2-second granularity (resolution), this allowed
them to fit the "seconds" part of the time into 5 bits, so that the
whole thing fit in 16 bits (5 bits for the hour, 6 for the minute).

As for updating, I don't think there's any behavior in Windows which
caches the writes to the directory but fails to return the cached data
on a read. That would cause very serious disk integrity problems all
over the place. It might well be that there is a delay in writing the
cache back to the disk (probably dependent on activity, not a fixed 30
seconds), but the cached data is also provided on a read so it doesn't
matter if it is physically on disk or not.

A problem with properly waiting for the app (Notepad) to finish seems
much more likely than a caching design that's as fundamentally
incorrect as what you describe.

--
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org