[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
RE: upgrade the severity of the "clock jump" warn, and ask people
- To: <or-talk@xxxxxxxxxxxxx>
- Subject: RE: upgrade the severity of the "clock jump" warn, and ask people
- From: "Ge van Geldorp" <ge@xxxxxx>
- Date: Mon, 19 Jun 2006 16:42:06 +0200
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Mon, 19 Jun 2006 10:42:27 -0400
- In-reply-to: <20060614222819.0931C140702F@moria.seul.org>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- Thread-index: AcaTrokYRGlln056RcWggL481l0mJg==
> From: arma@xxxxxxxx
>
> Log Message:
> upgrade the severity of the 'clock jump' warn, and ask people
> to report if it occurs.
From my log:
Jun 19 00:09:13.147 [info] connection_edge_finished_connecting(): Exit
connection to [scrubbed]:80 ([scrubbed]) established.
Jun 19 00:09:13.257 [info] connection_edge_finished_connecting(): Exit
connection to [scrubbed]:80 ([scrubbed]) established.
Jun 19 00:10:30.560 [warn] Please report: your clock just jumped 77 seconds
forward; assuming established circuits no longer work.
Jun 19 05:10:28.369 [info] connection_edge_package_raw_inbuf(): called with
package_window 0. Skipping.
Jun 19 05:10:29.280 [info] connection_edge_package_raw_inbuf(): called with
package_window 0. Skipping.
Jun 19 05:11:35.580 [warn] Please report: your clock just jumped 65 seconds
forward; assuming established circuits no longer work.
GvG