From: Christian Boltz <netdev-vger-kernel.org-/+gSslFCPOGzQB+pC5nmwQ@public.gmane.org>
To: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Feature request: "inverted" ping -a (beep on failure)
Date: Fri, 15 Apr 2011 21:35:32 +0200 [thread overview]
Message-ID: <201104152135.33171@tux.boltz.de.vu> (raw)
Hello,
ping -a (beep on ping success) is a quite useful command, but it can be
annoying.
I'd like to have the exact opposite of it: beep when pinging fails.
I understand that this is slightly difficult because "ping success" is
easier to detect (incoming package) than "ping failure" (no incoming
package or firewall reject) - my proposal is to have a timeout for every
package (if no reply package comes in) and beep if no reply is seen
after the timeout is over.
For the timeout, the -W option could be used. The default timeout seems
to be 10 seconds, which is OK.
Usecase / why this would be useful for me:
Basically for server monitoring. The exact usecase is that I have rented
a "root server" and asked the hoster to exchange a broken harddisk.
With the "inverted" ping -a, it would be easy to notice when they switch
off the server to replace the disk.
Please consider this feature for the next version of ping ;-)
(The iputils homepage does not list any bugtracker or similar, therefore
I'm asking here.)
Gruß
Christian Boltz
--
"we will support any library from any repo combined with
any application" is something that NO ONE does.
Or if they do, they are insane, or lying, or both.
[Greg KH in opensuse-factory]
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-04-15 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 19:35 Christian Boltz [this message]
2011-04-15 19:49 ` Feature request: "inverted" ping -a (beep on failure) Randy Dunlap
2011-04-15 20:10 ` Denys Fedoryshchenko
[not found] ` <20110415124937.6e746646.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-04-15 20:11 ` Christian Boltz
2011-04-15 20:14 ` Randy Dunlap
2011-04-15 21:57 ` Martin Topholm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201104152135.33171@tux.boltz.de.vu \
--to=netdev-vger-kernel.org-/+gsslfcpogzqb+pc5nmwq@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).