On Mon, 14 Feb 2000, Olaf Seibert wrote:

> On Thu 10 Feb 2000 at 18:03:18 +0100, Krister Walfridsson wrote:
> > That read should not hang as I understand it, so I think it is a kernel
> > issue. 
> 
> I think the same, because arpwatch also just stops functioning after
> a while. I think both programs use the packet filter, right?
> 
> The time it takes before arpwatch just stops detecting anything seems
> to vary, it seems to get faster over time. Maybe it is related to the
> size of its database (in which case the problem may not be the same as
> with rarpd anyway). 

	Its not a packet filter problem with rarpd - its the fact it opens
	the routing socket, then ignores it until too many updates build
	up. Could you debug arpwats and find out if its hanging on a
	read() on the routing socket?


		David/absolute