Re: write_to_descriptor bug

From: George Greer (
Date: 09/10/02

On Tue, 10 Sep 2002, Tap3w0rm wrote:

>> It means some user had so much data that the kernel's socket buffer is
>> full, CircleMUD's internal buffer is full, and they were sent yet more
>> information. At that point there's nowhere to put the data so they get
>> punted from the MUD.  It shouldn't crash you though.
>George are you basicly saying that the guy is not sending data and
>clearing his buf's often enough ?

He can't receive information fast enough to keep up with what you're

>and what is the max data you can add to a buf ... i jsut redid my score
>screen and only do a send to char once the end of it. am i doing smoethign
>wrong? shoudl i send daya to the user more often ?

See MAX_SOCK_BUF, then add your kernel's socket buffer (32k? 64k?).

George Greer

   | FAQ: |
   | Archives: |
   | Newbie List:   |

This archive was generated by hypermail 2b30 : 06/25/03 PDT