It would appear on my system that innd fails to work correctly. In
particular, a "ctlinnd newgroup blargh" will reliably result in the
following:
Apr 16 01:00:52 brucehall19 innd[347]: SERVER cant recv CCreader Bad
address
Apr 16 01:00:52 brucehall19 kernel: Exception at [<c014b03e>] (c01899c0)
Apr 16 01:01:04 brucehall19 kernel: Exception at [<c014b03e>] (c01899c0)
Apr 16 01:01:04 brucehall19 innd[347]: SERVER cant recv CCreader Bad
address
ctlinnd hangs around trying to get something back from the control pipe,
and does not return. I don't really have time to look at innd to see
what's going on - I've got Uni work to do, so promptly decided to install
(what turned out to be) a _really_ nasty RPM which trashed all of my news
stuff.
This may have been broken prior to 2.1.34, but is not under 2.1.29.
I believe these are the bits out of System.map that are relevant, but I'm
not _that_ sure....
c0143a60 T proc_unregister
c0143ae0 t proc_self_followlink
c0143b40 t proc_self_readlink
c0143bc0 T proc_root_init
and
c01886d0 t number
c01888d0 T vsprintf
c0188da0 T sprintf
c018a2b2 ? common_fixup
c018a2bd ? src_access_fault
later,
Peter Barker <AKA: Talon> | N ,-_| \ /---- Moree, NSW
Year: 3 Course: Engineering/Sci | W + E / ./}
p.barker@bohm.anu.edu.au | S \_,-._*<-- Canberra
http://brucehall19.anu.edu.au | v [35S, 149E]