Using Arpwatch version 2.1a13-2.1 on a dual NIC host that performs routing and a few services for a three stations LAN, I have also encountered surprisingly high CPU usage - arpwatch was competing with other running processes to hog the whole single core CPU. Restarting arpwatch solved the problem. I don't know how long arpwatch had been running wild - probably a few days at least, and I do not know what triggered this behavior either.
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
