[liboping-changes] octo's ping library: Changes to 'master'

[Florian Forster]

 src/mans/oping.pod |   44 ++++++++++++++++++++++++++++++++++++++++++++
 src/oping.c        |   13 ++++++++++++-
 2 files changed, 56 insertions(+), 1 deletion(-)

New commits:
commit 0e8b1b239fdcf9307a14d57c1620843e86932583
Merge: 6949f72 d908d5a
Author: Florian Forster <ff at octo.it>
Date:   Thu Aug 18 06:58:53 2016 +0200

    Merge branch 'pr/6'

commit d908d5abd442e491fe81af8aaf5e53a599b941f2
Author: Antoine Beaupré <anarcat at koumbit.org>
Date:   Mon Oct 5 16:09:38 2015 -0400

    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