unwanted.log strangeness

[Steven L. Sesar]

In the following setup, reader_old is due to be replaced by reader_new.
I have had the new reader spooling for a few weeks now, and have noticed
something strange. The unwanted.log entries differ between both reader
machines. Normally, I wouldn't care, but in this case, one of our ~160
local.* newsgroups are showing up in the unwanted.log file on
reader_new. control.ctl, newsfeeds are identical on both readers. Why
would only one local.* newsgroup find its way to unwanted.log under
these circumstances?

feeder (transit-only): which feeds an identical subset of a public feed
to:
            reader_old: feeds reader_new local.*
            reader_new