aboutsummaryrefslogtreecommitdiff
path: root/networking/ping6.c
diff options
context:
space:
mode:
authorRob Landley <rob@landley.net>2006-06-21 00:52:31 +0000
committerRob Landley <rob@landley.net>2006-06-21 00:52:31 +0000
commit2d6af16035cf71b5e08b3f87c482feb12be31c0e (patch)
tree3fab440445e176d1c93d950c8b77c7f7c221b305 /networking/ping6.c
parentb049c0ec196fe3fd89c0b92b3d2d70bce095fba0 (diff)
downloadbusybox-2d6af16035cf71b5e08b3f87c482feb12be31c0e.tar.gz
Zubicaray reported a bug in vi that causes it to eat 100% cpu when you close
an xterm it's running in. The vi signal behavior would catch and restarts lots of signals, like SIGHUP, that should just kill the thing. (Leftover behavior from when it would segfault all the time.) Filtered out the more obviously bad ones. If it segfaults, we should find and fix the problem.
Diffstat (limited to 'networking/ping6.c')
0 files changed, 0 insertions, 0 deletions