author | Antoine Beaupré <anarcat@koumbit.org> | |
Mon, 5 Oct 2015 20:09:38 +0000 (16:09 -0400) | ||
committer | Antoine Beaupré <anarcat@debian.org> | |
Wed, 17 Aug 2016 18:30:47 +0000 (14:30 -0400) | ||
commit | d908d5abd442e491fe81af8aaf5e53a599b941f2 | |
tree | 8ca34855541b25b3cc8be72a3e65eabc77eb0702 | tree | snapshot |
parent | 48acd61a5c6257cae2df205467caa0a91c2b0d1c | commit | diff |
add bell output on successful pings
the rationale here is that it's actually pretty hard to do this with a
regular ping. you need a silly shell loop and it doesn't always work
right everywhere, because the output of the system ping is
platform-dependant. it also buffers stdout in some weird ways sometimes.
therefore, i think it's a great addition to oping.
the purpose of this is that it can be useful to "hear" ping packets
come back when doing network diagnostics. obviously, this will be
useless in finding out *failed* hosts if multiple hosts are selected,
as any sucessful host will produce a beep. but it can nevertheless be
used to trace network cables or problems without looking at the
console. i also use audible pings to let me know when a hosts returns
after a reboot.
Note that I had to struggle quite a bit to make my terminal bell work,
the following articles were used to generate documentation on how to
make that work reliably:
https://askubuntu.com/questions/228096/terminal-bell-doesnt-ring
also see the following for the original inspiration for this:
http://catb.org/jargon/html/P/ping.html
https://groups.google.com/forum/#!msg/comp.sys.next/JDaeD8oqarU/v8xaDS8kXM0J
the rationale here is that it's actually pretty hard to do this with a
regular ping. you need a silly shell loop and it doesn't always work
right everywhere, because the output of the system ping is
platform-dependant. it also buffers stdout in some weird ways sometimes.
therefore, i think it's a great addition to oping.
the purpose of this is that it can be useful to "hear" ping packets
come back when doing network diagnostics. obviously, this will be
useless in finding out *failed* hosts if multiple hosts are selected,
as any sucessful host will produce a beep. but it can nevertheless be
used to trace network cables or problems without looking at the
console. i also use audible pings to let me know when a hosts returns
after a reboot.
Note that I had to struggle quite a bit to make my terminal bell work,
the following articles were used to generate documentation on how to
make that work reliably:
https://askubuntu.com/questions/228096/terminal-bell-doesnt-ring
also see the following for the original inspiration for this:
http://catb.org/jargon/html/P/ping.html
https://groups.google.com/forum/#!msg/comp.sys.next/JDaeD8oqarU/v8xaDS8kXM0J
src/mans/oping.pod | diff | blob | history | |
src/oping.c | diff | blob | history |