I haven't been around in quite a while between domestic obligations and overseas travel, so I'm sorry if this comes off as a Johnny come lately sort of post. I'm unsure if this has been suggested in one fashion or another - be it this thread or another, but here I go:
This would likely be somewhat of a project itself, but would some sort of standard testing script that generates it's own log file and perhaps, one or more csv files be helpful. I'm thinking of something that could be run from say, a couple of days to a week, in order to generate necessary data. I just don't know if this is a feasible or practical thing, but over the years I've noticed requests for people to test out various components for performance and/or bug issues. And a lot of well intentioned people here, myself included unfortunately, don't always provide the detailed information that could really be helpful. I know that at work if I'm constantly going through endless event logs, I get almost nowhere or even worse, I'm searching for a red herring because of how I interpreted a few log entries. But when I use an event log aggregator / analyzer, things suddenly become much more clear. I know it isn't the perfect analogy, but hopefully you get the idea.
I'd have no problem at all flashing a beta and then running some sort of test suite and submitting the data, but now more than ever (we're expecting our first little one) I don't have the time, and quite frankly the expertise, to be digging around my router half blind. My Linux / Busy Box skills are and will likely remain at the advanced beginner level. I've been nose first into computers in one way or another since about 1984 myself and at this point I've realized this is a young man's game. I'm not going to be jumping up to an advanced level of expertise in anything that I'm not already at.
