Description of Problem:
When restarting portsentry after an attack CPU usage peeks (top, about
75% CPU usage on this 1GHz Pentium system). This condition goes on (at
least for minutes) until portsentry is restarted another time.
Not sure if this is a portsentry or maybe an init script issue.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch an attack from a system (fe telnet 10.10.10.10 6667). Repeat if
necessary (twice in this configuration).
2. Issue "service portsentry restart" on the attacked system.
3. Run top to monitor CPU load
CPU load peak.
Normal CPU usage.
This state only occurs when KILL_RUN_CMD is not specified.
Specifying a KILL_RUN_CMD solves the issue.
Maybe catch an empty KILL_RUN_CMD?
Closing as WONTFIX due to end of life of the Power Tools product line. Please
open a new bug report under the Red Hat Linux product if the component is still
included in the base Red Hat distribution.