On Tue, May 6, 2008 at 10:06 AM, Scott Ullrich <[EMAIL PROTECTED]> wrote: > Show the process information (ps awux | grep ping). It is normal for > this process to be running quite a bit but I am not sure about 8 > hours.
root 59637 5.7 0.5 1744 1216 ?? S 7:51PM 58:41.28 /bin/sh /etc/ping_hosts.sh root 1510 0.0 0.3 1268 732 ?? Is 2:06PM 0:00.04 minicron 240 /var/run/ping_hosts.pid /etc/ping_hosts.sh root 59636 0.0 0.5 1716 1176 ?? I 7:51PM 0:00.01 sh -c /etc/ping_hosts.sh root 88640 0.0 0.5 1744 1216 ?? S 11:12AM 0:00.00 /bin/sh /etc/ping_hosts.sh The box was rebooted around 2pm. The high CPU utilization started right before 8pm, you can see how the first ping_hosts.sh script has used over an hour of CPU time. The script itself doesn't take up that much CPU, but looking at top CPU time is 25-30% user and 60-70% system, 0% idle which seems to indicate that the script is forking off a lot of processes. I was making some changes to the NAT rules and number of states to track around the time to see how pfsense would handle a SYN flood. Looking at the script itself, I don't see any obvious places where the script could get stuck. If it were possible to see what the script was doing that would help. I don't think I mentioned this earlier, but it's running 1.2 embedded on ALIX hardware. -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
