On Wed, 24 May 2006 21:32:46 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> output, not very easy to interpret. But it shouldn't be hard to find the > sections where the 29 timeouts and resets occur, just by searching for > large jumps in the timestamps. I suggest looking for -104 (unlink). It can be done with grep. Use space to prevent grep from interpreting the dash: grep " -104" mon.out But comparing timestamps requires a custom perl or python script. Not an insurmountable obstacle for a hacker, I'm sure, but still... > If you post the region surrounding one of > those occurrences, I can tell you what's going on. Right. -- Pete ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
