More on SITEreader log entires
rra at stanford.edu
Sun Mar 10 18:40:32 UTC 2002
Jeffrey M Vinocur <jeff at litech.org> writes:
> On Fri, 8 Mar 2002, William F. Maton wrote:
>> #0 0x80756c6 in SITEreader (unused=0x401ea8cc) at site.c:27
>> #1 0x806998d in CHANreadloop () at chan.c:1093
>> #2 0x806ba94 in main (ac=2, av=0xbffffe94) at innd.c:649
>> I'm not sure if this helps anyone with finding out why SITEreader()
>> getscalledso often.
> It doesn't help, unfortunately -- we always loop over it, but the question
> is why it appears that there's data to read.
Do we already know which channel in particular is triggering that check?
We should be able to figure it out by printing out the argument to
SITEreader inside gdb.
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the inn-bugs