[ntp:questions] Re: ACTS - too many recvbufs allocated (40) (Correct the Version of ntp-dev)

David L. Mills mills at udel.edu
Fri Feb 11 01:46:35 UTC 2005


Danny,

FreeBSD rackety.udel.edu is currently victim of the bug. It replaced the 
old SunOS IPC in service for 16 years. You have the keys to the kingdom.

Dave

mayer at gis.net wrote:
> ----- Original Message Follows -----
> 
>> >> to:
>> >>          rb->recv_length =
>> >>              read(fd, (char *)&rb->recv_space, (unsigned)i);
>> >>
>> >>          if (rb->recv_length <= 0 || errno != 0)
>> >>          {
>> >>                  netsyslog(LOG_ERR, "clock read fd %d: %m", fd);
>> >>                  freerecvbuf(rb);
>> >>                  goto select_again;
>> >>          }
>> >>
>> >> This should take care of the problem. I will put a better fix into
>>the
>> >> sources over the next few days.
>>
>> >That addresses the symptom rather than the cause, which is a hangup
>> >owing to carrier dropping.  With the above change in place, I'd
>>expect
>> >a continuous stream of "clock read" messages, CPU maxed, and no
>>other
>> >input will happen because "goto select_again" picks up the error
>>condition
>> >each time round and never does anything else.
>>
>>Yes, this happens (100% proc consumed, infinite select loop, no other 
>>input) , as I wrote in some of my previous comments.
>>-cipo
>>
> 
> 
> Oh, I missed that. I have nowhere to test this. Do you know what the
> error is? I'll try and take another look at it.
> 
> Dannny
> 



More information about the questions mailing list