Description of problem: server is full Version-Release number of selected component: fping-3.4-1.fc18 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: fping -r 30 -B 1 -q 192.168.1.254 crash_function: send_ping executable: /usr/sbin/fping kernel: 3.9.11-200.fc18.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (2 frames) #0 send_ping at fping.c:1596 #1 main_loop at fping.c:1110
Created attachment 779293 [details] File: backtrace
Created attachment 779294 [details] File: cgroup
Created attachment 779295 [details] File: core_backtrace
Created attachment 779296 [details] File: dso_list
Created attachment 779297 [details] File: environ
Created attachment 779298 [details] File: limits
Created attachment 779299 [details] File: maps
Created attachment 779300 [details] File: open_fds
Created attachment 779301 [details] File: proc_pid_status
Created attachment 779302 [details] File: var_log_messages
Issue reported, waiting for upstream.
Confirmed. This issue has been fixed since 3.5 version. Please wait the packager to push an update.
fping-3.5-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fping-3.5-1.fc18
Package fping-3.5-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fping-3.5-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-13892/fping-3.5-1.fc18 then log in and leave karma (feedback).
fping-3.5-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.