On Sat, 19 Jan 2008, Dave Mielke wrote:
[quoted lines by Stéphane Doyon on 2008/01/18 at 22:41 -0500]
There are actually two alternating write errors: one from writeData() or
something underneath it, plus the LogError("Baum Bluetooth write");. The
alternation prevents syslog from collapsing the messages, so your disk
starts crunching...
We should perhaps ignore only specific recognized errors, and reset on
anything else (and not just ENOTCONN), like we do for reads.
Please try the latest code and let me know how it works.
Yes, looks good.
Thanks!
--
Stéphane Doyon
<[EMAIL PROTECTED]>
http://pages.videotron.com/sdoyon/
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://mielke.cc/mailman/listinfo/brltty
