Comment 3 for bug 357462
Revision history for this message
| prower2000@hotmail.com (prower2000-gmail) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I can confirm that this bug exists in Karmic's version of arpwatch as well. Steps to reproduce:
1) start arpwatch running (or install it, it's started automatically if you do)
2) disable networking to your PC via the NetworkManager applet and re-enable it
3) check top, arpwatch is now using up 100% CPU in the background and continues to do so until restarted