2011-05-02, 09:40 PM
sub Wrote:The log files already exist for that purpose. I dont see any reason for hotkey, and doing it after an error isnt going to result in useful logging. You need any detailed logging turned on at the time the problem happens.
I mean if logging is set to normal, to set it to max level.
While it might not show the reason why it failed the first time around, it would have the needed data once the log level is set to the max level on the next time you try it--as least, I would think it would.
Otherwise, you must exit the program, and run config, and set the logging level, then rerun the program.
I guess it might also be possible to check the file size, and on detection of a 0 byte file, to set max logging level, and retry the last command, and try that a few times before giving up.