Possible issue re-aquiring log files if an application deletes, moves, or renames, the original before creating a new one

[mikeloeven]

I was doing some debugging in Kerbal Space program the other day and I noticed that tail blazer would not tail the log after the game crashed and was restarted. I believe this has to do with the fact that on a crash the game will create a new folder for the crash dump and than move the log file into that folder. on the next run of the program it will create a new log file of the same name in the same location however tail blazer does not seem to be able to re-acquire the tail unless the log file is manually opened again.

On a side note this seems to occur more often if the log was cleared prior to relaunching the application possible alternate cause of the issue

[RolandPheasant]

I have also noticed those behavior recently. In older versions it behaved as expected so hopefully that will make it easier for me to hunt down the problem.