On Sun, Feb 13, 2000 at 11:07:17PM -0500, Mark Lynn wrote: > > Obviously, I've screwed something up somewhere, but don't know what. > Any guess as to what's going on? Is there any particular significance > to port 832? I didn't see it listed in the services. What on meeko could > be attempting to open this port? Further, why does tcplogd keep spawning > new processes that don't go away? > > I realize that iplogger is being replaced, but would really like to > understand > this problem before I explore upgrading packages.
that is the problem with iplogger, run the following: apt-get install ippl apt-get --purge remove iplogger that will solve the problem -- Ethan Benson
