From: "Писковой Иванъ" <piskovoyivan@gmail.com>
To: ALT Linux Community general discussions <community@lists.altlinux.org>
Subject: [Comm] Глюк в ping
Date: Thu, 18 Dec 2014 21:23:35 +0800
Message-ID: <2586900.d8bLN0C133@vanyabook.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]
Здравствуйте.
Нашёл вот глюк в статистике ping. Не пойму только от чего. То ли от долгого
времени прохождения пакета, то ли от большого их количества.
$ ping 8.8.8.8
...
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
64 bytes from 8.8.8.8: icmp_req=29875 ttl=40 time=258769 ms
64 bytes from 8.8.8.8: icmp_req=29876 ttl=40 time=266647 ms
ping: sendmsg: No buffer space available
64 bytes from 8.8.8.8: icmp_req=29877 ttl=40 time=305176 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
64 bytes from 8.8.8.8: icmp_req=29908 ttl=40 time=293655 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
ping: sendmsg: Network is unreachable
^C
--- 8.8.8.8 ping statistics ---
95537 packets transmitted, 78907 received, 17% packet loss, time 272139897ms
rtt min/avg/max/mdev = 236.893/13544.079/305176.170/-136944034303.-555 ms,
pipe 95
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2014-12-18 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 13:23 Писковой Иванъ [this message]
2014-12-18 16:41 ` Hihin Ruslan
2014-12-18 17:06 ` Писковой Иванъ
2014-12-18 17:27 ` Hihin Ruslan
2014-12-19 12:40 ` Vasily Tereshko
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=2586900.d8bLN0C133@vanyabook.localdomain \
--to=piskovoyivan@gmail.com \
--cc=community@lists.altlinux.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
ALT Linux Community general discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
public-inbox-index community
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git