Improving game logging
Posted: Mon Dec 17, 2012 4:22 am
A recent case of missed opportunity here reminded me of something I'd been meaning to suggest for a while.
There are regular instances where logs recording difficult-to-reproduce errors aren't available, because the player has inadvertently wiped out the log by having re-run the game 2 or more times since the problem manifested. Indeed, I'm sure most of us here have at some point wished we had access to a logfile that no longer exists. I've even considered writing a bash-script that would auto-run just prior to launching Oolite that would back up both currently existing logs to a sub-folder. In fact, I think I will do so, to address the shortcomings of the logging on 1.76.1.
Please consider extending the log-rotation system so that (say) the last dozen or even 20 game-logs are retained, instead of the most recent two logs only.
There are regular instances where logs recording difficult-to-reproduce errors aren't available, because the player has inadvertently wiped out the log by having re-run the game 2 or more times since the problem manifested. Indeed, I'm sure most of us here have at some point wished we had access to a logfile that no longer exists. I've even considered writing a bash-script that would auto-run just prior to launching Oolite that would back up both currently existing logs to a sub-folder. In fact, I think I will do so, to address the shortcomings of the logging on 1.76.1.
Please consider extending the log-rotation system so that (say) the last dozen or even 20 game-logs are retained, instead of the most recent two logs only.