From: Junior <ej...@in...> - 2007-12-13 14:25:07
|
Could anyone more familiar with lircd tell possible reasons why it would = stop polling? For some reason, it would stop polling causing the receive buffer to be = full and hence the overrun message. I'm thinking the only way that could happen is if there is a bug in the = lircd daemon. Has anyone ran into this before? Thanks, --Jr. > -----Original Message----- > From: ejr=40inbox.com > Sent: Wed, 12 Dec 2007 07:13:37 -0800 > To: lirc-list=40lists.sourceforge.net > Subject: Buffer Overrun >=20 > Hi All, > I've noticed after a while I get a buffer overrun error with irw. > Does anyone know of a problem with this? > Is there a problem with irw? Socket? >=20 > Thanks, > --Jr. >=20 > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php |