Bruce,
while we're discussing log file issues, here is another feedback, especially for the production versions:
Whenever you use log files being written directly from the emulator, please consider to think about - and eventually implement - some kind of automatic log file maintenance.
I've seen cases where something happened and a running emulator wrote a multi GB log file. I've even seen a case, where an emulator log file overflowed the Windows disk.
In those cases, you don't want to stop 'production' to just reset the log file or even try to look at it. As I explained before, it's easy with Putty: you can re-start the log file while running.
For log files written directly by the emulator, consider:
- specify maximum size and have emulator automatically create a new file and save the old one (with ;-1)
- specify maximum lifetime (30 days) of the log file
- create some mechanism to reset the log file(s) based on some 'signal' received from an external program
Log files are an improvement versus real Alphas, but they can also create new problems.
Volker.
