Innfeed coredumps

bill davidsen davidsen at tmr.com
Tue Nov 5 20:06:49 UTC 2002


In article <ylfzugj13r.fsf at windlord.stanford.edu>,
Russ Allbery  <rra at stanford.edu> wrote:

| Well, I'm not sure exactly what's causing this problem, but I can give you
| some more background.  This error message indicates that you're getting a
| 437 response from some peer while innfeed doesn't think that you've sent
| any articles to the peer.
| 
| Which peer it is you should be able to determine by running gdb on that
| core file and the innfeed binary and looking at the value of
| cxn->myHost->params->hostName.
| 
| I think the chances are that this indicates some sort of problem with one
| of your peers sending the wrong NNTP responses, but it could be a bug in
| innfeed somewhere.  innfeed is very picky about NNTP responses and doesn't
| deal well with getting things that it doesn't expect; that really needs to
| be cleaned up.

  I once had a thought that one could do a "suck feed" for a given
message-id by faking a "send me" response for the id as if a check had
been sent. I looked at the code in Earthquake and that definitely won't
work, I have dropped myself a note to look at innfeed as well (and maybe
innxmit while I'm looking).

  I don't know that this is a problem in any way, just... untidy code.
Hopefully innfeed is indeed very picky.

-- 
bill davidsen <davidsen at tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.


More information about the inn-workers mailing list