If you have a system dumping stuff to the log with enough verbosity that the flush interval is 30+ minutes¡ take the half hour to go get yourself a stiff drink and wait for the log to flush naturally (GD&R
?)
I remember once watching Toine explaining about how they had to change the rules on how often the processor writes stuff to the Plogs to avoid issues like the flash memory wear-downs on the beloved MC3's...
Question is, let's say I'm troubleshooting a system, I see the errors, and the flush interval has been increased to 32 minutes.... is there a way for me to force-flush just so I can grab the PLog file for further analysis?
Alternatively, I know I can always print err on the console and grab that, but sometimes it would be nice to just have the complete PLog file...