00:00:12  * Michalikjoined
00:04:41  * kostcojoined
00:19:32  * DarkGodquit (Ping timeout: 265 seconds)
00:37:54  * hdmsquit (Quit: hdms)
00:53:13  * Guest14434joined
00:53:20  <Guest14434>hi
01:20:41  * Guest14434quit (Quit: Leaving)
02:18:37  * Something12joined
05:17:01  * SkyRocknRolljoined
07:29:38  * DarkGodjoined
08:52:03  * SkyRocknRoll_joined
10:05:49  * SkyRocknRoll_quit (Ping timeout: 255 seconds)
10:20:21  * SkyRocknRoll_joined
12:02:22  * SkyRocknRoll_quit (Ping timeout: 255 seconds)
12:14:58  * hdmsjoined
13:49:18  <rphillips>good morning
14:26:37  * dan336joined
14:48:57  <creationix>morning
14:50:49  <creationix>rphillips: do you know about the timestamp embedded in ping bodies?
14:51:23  <creationix>does it have to be a certain format? the command-line ping seems to use seconds + nanoseconds (or maybe microseconds) as 8bytes
14:51:46  <creationix>but I think all I need is any monotonic value to compare timings from before and after
14:53:04  <rphillips>i believe that is correct
14:53:15  <rphillips>i don't know much about it
14:53:25  <rphillips>http://www.networksorcery.com/enp/protocol/icmp/msg13.htm
14:53:29  <rphillips>it might be in RFC 1122
14:58:59  <creationix>yeah, I saw icmp timestamp, but this is icmp echo
14:59:17  <creationix>well, I’ll just use uv.hrtime for now, it shouldn’t matter
14:59:23  <creationix>ping is just a hack on top of echo anyway
15:00:28  <creationix>getting realtime timestamp in luvit is actually hard since libuv doesn’t provide it (It’s part of JS)
15:00:48  <creationix>and darwin doesn’t support the normal unix methods, nor does windows
15:02:10  <rphillips>gotcha
15:54:06  * SkyRocknRollquit (Remote host closed the connection)
18:21:27  * piernovquit (Ping timeout: 240 seconds)
18:29:51  * piernovjoined
18:52:56  * endoujoined
18:53:25  * endou_quit (Write error: Connection reset by peer)
19:30:20  <creationix>rphillips: how do you know if a ping check is ipv4 or ipv6?
19:30:24  <creationix>don’t they just pass us hostnames
19:30:27  <creationix>luvit.io has both
19:30:30  <creationix>(for example)
19:31:29  <rphillips>There is also a config option on the check for ipv4 and IPv6 or one or the other
19:32:47  <creationix>so ping’s only attribute is “count” right? http://docs.rackspace.com/cm/api/v1.0/cm-devguide/content/appendix-check-types-remote.html#section-ct-remote.ping
19:33:09  <rphillips>http://docs.rackspace.com/cm/api/v1.0/cm-devguide/content/service-checks.html
19:33:15  <rphillips>Target_resolver
19:33:46  <rphillips>Yes. And count is optional.
19:33:57  <creationix>ok, and it will be the string “IPv4” or “IPv6” and if not specified, I should use just whatever comes back first?
19:35:34  <rphillips>Correct. I think those strings are case insensitive.
19:35:50  <creationix>good idea
19:36:10  <creationix>now if only I can figure out why the second ping on the same kind always hangs
19:36:25  <creationix>I can ping an ipv4 and then an ipv6, but the second time I try either, nothing happens
19:36:53  <creationix>I’m creating a new socket and closing the old one to keep things simple, I havn’t tried connection pooling yet
19:37:06  <creationix>(though I’m not sure what that means for raw sockets over uv_udp_t)
19:49:54  * piernovquit (Ping timeout: 250 seconds)
19:52:07  * DarkGodquit (Ping timeout: 240 seconds)
19:52:42  * piernovjoined
21:27:20  * rchquit (Changing host)
21:27:20  * rchjoined
23:14:12  * dan336quit (Quit: Leaving.)
23:25:53  * dan336joined