I will test and report back. Thank you.

Hi,

I just wanted to let you know that we have now released LogViewPlus v3.1.21 as a BETA release.

This release attempts to address the network share / tail issue discussed above.  As mentioned, we do not have the ability to test for this particular issue, so we have had to make some assumptions.  If you do find time to verify the fix on your end, I would appreciate it.

Hope that helps!

Toby

+x

 

LogViewPlus Support - 27 Mar 2025

Thanks for reporting this issue.

I am not able to reproduce the issue, but I think the problem here is how the Windows file share is caching data.  LogViewPlus works by checking the file size in Windows.  If the file size is cached and not changed, LogViewPlus does not attempt to read the file.

The fact that VS code doesn't have the issue is interesting.  VS code isn't asking for file size, it is actually reading the file, and maybe this operation is forcing a cache refresh?  I would be happy to modify our next BETA if you would be able to test for us.  Again, we are not able to reproduce the issue.

Thanks again,

Toby

Thank you for the quick answer. The issue may be hard to reproduce, because the files are hosted on a HyperV machine which is in turn hosted on VMWare ESXi.

The VS Code fix works partially. In general the behavior seems to be that changes are updated for a while after opening the file. And afterwards at some point they stop. With VS Code the time between updates and the time till the updates stop seem to be higher. But I have seen a case where both VCode and LogViewPlus had to be forced to refresh.

I would be happy to test. I could do some more in depth analysis with a fix candidate

Thanks for reporting this issue.

I am not able to reproduce the issue, but I think the problem here is how the Windows file share is caching data.  LogViewPlus works by checking the file size in Windows.  If the file size is cached and not changed, LogViewPlus does not attempt to read the file.

The fact that VS code doesn't have the issue is interesting.  VS code isn't asking for file size, it is actually reading the file, and maybe this operation is forcing a cache refresh?  I would be happy to modify our next BETA if you would be able to test for us.  Again, we are not able to reproduce the issue.

Thanks again,

Toby

Log files do not update after initial load. As the logs are written no new entries appear in LogViewPlus. Sometimes the additional lines would be reloaded — but only after >2 minutes (approximate) if at all. This happens for files opened on a shared windows drive on another machine. The files are specified by a directory monitor.

I have a workaround. If I keep the log file open in parallel in the background in both VS Code and LogViewPlus, the LogViewPlus updates seem to be immediate. But this is an awkward solution. The VS Code workaround is not reliable.