23 Nov
2011
23 Nov
'11
9:16 p.m.
It's quite common for me to ping a server while it's down. Often when doing
so I have a rough idea of how long it will take (for example rebooting the new
Hetzner servers I'm running in Germany takes about 160 seconds during which
there are no ping responses) so it's good to know how long it is before I
should expect a response. At other times I want a running count of how long
it's been down so I can give an accurate complaint when someone answers my
call.
The standard ping programs tell you the packet count (which by default is 1
per second) when it receives a response. When there is no response nothing is
printed.
I would like a ping type program which will tell me how many seconds the
target has not been responding for.
Does anyone know of such a program?
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
23 Nov
23 Nov
9:27 p.m.
I have been using smokeping (http://oss.oetiker.ch/smokeping/) which
gives a view at availability and link quality as well.
regards
Slav
-----Original Message-----
I would like a ping type program which will tell me how many seconds the
target has not been responding for.
Does anyone know of such a program?
"This e-mail and any attachments to it (the "Communication") is, unless
otherwise stated, confidential, may contain copyright material and is for the use only of
the intended recipient. If you receive the Communication in error, please notify the
sender immediately by return e-mail, delete the Communication and the return e-mail, and
do not read, copy, retransmit or otherwise deal with it. Any views expressed in the
Communication are those of the individual sender only, unless expressly stated to be those
of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its
related entities including ANZ National Bank Limited (together "ANZ"). ANZ does
not accept liability in connection with the integrity of or errors in the Communication,
computer virus, data corruption, interference or delay arising from or in respect of the
Communication."
9:35 p.m.
On 23/11/2011, at 21:16, Russell Coker <russell(a)coker.com.au> wrote:
It's quite common for me to ping a server while
it's down. Often when doing
so I have a rough idea of how long it will take (for example rebooting the new
Hetzner servers I'm running in Germany takes about 160 seconds during which
there are no ping responses) so it's good to know how long it is before I
should expect a response. At other times I want a running count of how long
it's been down so I can give an accurate complaint when someone answers my
call.
The standard ping programs tell you the packet count (which by default is 1
per second) when it receives a response. When there is no response nothing is
printed.
I would like a ping type program which will tell me how many seconds the
target has not been responding for.
Does anyone know of such a program?
I find mtr great for this sort of thing. It will report both the number of received
packets, as well as not received packets. The stats can also be reset at any time by
pressing 'r'
10:01 p.m.
On 2011-11-23 21:16, Russell Coker wrote:
It's quite common for me to ping a server while
it's down. Often when doing
so I have a rough idea of how long it will take (for example rebooting the new
Hetzner servers I'm running in Germany takes about 160 seconds during which
there are no ping responses) so it's good to know how long it is before I
should expect a response. At other times I want a running count of how long
it's been down so I can give an accurate complaint when someone answers my
call.
The standard ping programs tell you the packet count (which by default is 1
per second) when it receives a response. When there is no response nothing is
printed.
I would like a ping type program which will tell me how many seconds the
target has not been responding for.
Does anyone know of such a program?
I made a very cool discovery a couple of months ago: This can be done
with the 'ping' which ships with Debian Squeeze!
mattcen@owen:tmp$ dpkg -S $(which ping)
iputils-ping: /bin/ping
mattcen@owen:tmp$ dpkg -l iputils-ping
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Description
+++-=============-=============-===============================================
ii iputils-ping 3:20100418-3 Tools to test the reachability of network hosts
mattcen@owen:tmp$ ping -D adam
PING adam.lan (192.168.2.2) 56(84) bytes of data.
[1322045416.121969] 64 bytes from adam.lan (192.168.2.2): icmp_req=1 ttl=64 time=0.052
ms
[1322045417.123508] 64 bytes from adam.lan (192.168.2.2): icmp_req=2 ttl=64 time=0.059
ms
[1322045418.125086] 64 bytes from adam.lan (192.168.2.2): icmp_req=3 ttl=64 time=0.042
ms
[1322045419.127338] 64 bytes from adam.lan (192.168.2.2): icmp_req=4 ttl=64 time=0.059
ms
^C
--- adam.lan ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 0.042/0.053/0.059/0.007 ms
mattcen@owen:tmp$
Unfortunately, this -D option is rather new (for example it's not
available in Ubuntu 10.04), so may not be available on all hosts you
use; I'm still trying to work out exactly which version introduced the
change, but I can't seem to find the upstream repository.
--
Regards,
Matthew Cengia
10:15 p.m.
On 2011-11-23 22:01, Matthew Cengia wrote:
Unfortunately, this -D option is rather new (for
example it's not
available in Ubuntu 10.04), so may not be available on all hosts you
use; I'm still trying to work out exactly which version introduced the
change, but I can't seem to find the upstream repository.
Found it: http://www.skbuff.net/iputils/
The -D option was added between release iputils-s20071127 and
iputils-s20100214.
--
Regards,
Matthew Cengia
4140
days inactive
4140
days old
4 comments
4 participants
participants (4)
-
hannah commodore -
Matthew Cengia -
Pidgorny, Slav -
Russell Coker