Re: Clearing file cache to read what's really on disk
- Posted by AndyDrummond Feb 07, 2012
- 1483 views
Sorry, did I say it only happened with NetDrive? It also happens when I am at my desk looking at the file on the internal network. I can't make the logger write directly to a file actually located on my computer - it's not at a constant IP address.
I'll scan the two links above but I am pretty sure it's a Windows feature; they cache the file data when it has been read, and just give it back next time you ask for it. Same stuff as before. I should be able to flush the read cache, IMHO.
A
I have used logging files on winxpee to keep code sync'd across 8 computers on a dhcp lan, and other than the usual idiocy of winders, i have had no problem getting up-to-date data from the logging files, no matter which computer wrote to which file on any other computer, and at speeds up to 10 hits per second. I have more of a problem with winders suddenly and completely ignoring another computer on the lan, which isn't an Euphoria problem.
Reading more posts on this, i suggest you kill NetDrive and see if you can read the file's new data. I think it's an ownership issue in winders, and until NetDrive explicitly tells winders that it no longer owns the file, winders won't touch it with a ten foot pole to get updates to the file. Killing NetDrive won't be guaranteed to tell windows to allow other access, but it might.
useless
OK, now that IS interesting. I killed NetDrive and the problem seems to go away. That is, my log file reader keeps up with new logged data. I am now at the office and using the direct mapped drive. When I had NetDrive running, which I do to make access to our server easy at home, the thing didn't keep up. You might be right that if dear old Windoze is being held off by NetDrive then I would get the total update failure I was seeing. Hmmm. I think your username maybe rather inappropriate, Sir.
More tests called for, but two steps forward and one back is progress ...
A
