[00:14] *** dj_goku has quit IRC (Remote host closed the connection)
[00:14] *** dj_goku has joined #arpnetworks
[00:14] *** dj_goku has quit IRC (Changing host)
[00:14] *** dj_goku has joined #arpnetworks
[00:32] *** dj_goku has quit IRC (Remote host closed the connection)
[00:32] *** dj_goku has joined #arpnetworks
[00:32] *** dj_goku has quit IRC (Changing host)
[00:32] *** dj_goku has joined #arpnetworks
[00:55] *** dj_goku has quit IRC (Ping timeout: 245 seconds)
[00:55] *** dj_goku has joined #arpnetworks
[00:55] *** dj_goku has quit IRC (Changing host)
[00:55] *** dj_goku has joined #arpnetworks
[01:10] *** dj_goku has quit IRC (Ping timeout: 256 seconds)
[01:10] *** dj_goku has joined #arpnetworks
[01:10] *** dj_goku has quit IRC (Changing host)
[01:10] *** dj_goku has joined #arpnetworks
[01:16] *** dj_goku has quit IRC (Ping timeout: 245 seconds)
[01:17] *** dj_goku has joined #arpnetworks
[01:17] *** dj_goku has quit IRC (Changing host)
[01:17] *** dj_goku has joined #arpnetworks
[01:35] *** dj_goku has quit IRC (Quit: Lost terminal)
[05:08] *** layer8problem has joined #arpnetworks
[05:09] <layer8problem> does anyone know if there was maintenance work done in the last day to could have resulted in significant lag or hypervisor scheduling weirdness? I've got a bunch of 'time went backwards significantly' sort of log messages this morning that I don't normally see.
[09:52] *** ziyourenxiang has quit IRC (Ping timeout: 256 seconds)
[11:46] *** Stan___ has joined #arpnetworks
[12:05] *** Stan___ has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
[15:25] *** dferris has joined #arpnetworks
[15:59] *** ziyourenxiang has joined #arpnetworks
[16:19] *** ziyourenxiang has quit IRC (Ping timeout: 240 seconds)
[19:59] *** erratic has quit IRC (Ping timeout: 256 seconds)
[21:32] *** erratic has joined #arpnetworks
[23:40] *** Stan___ has joined #arpnetworks