[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Clock problems

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Clock problems
From: Paul Syverson <syverson@xxxxxxxxxxxxxxxx>
Date: Mon, 9 Mar 2009 13:45:33 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Mon, 09 Mar 2009 13:44:38 -0400
In-reply-to: <BLU120-W3726BAB47A3AC2D2179EB682A00@xxxxxxx>
References: <200903090642.n296gmFk026857@xxxxxxxxxxxxx> <BLU120-W3726BAB47A3AC2D2179EB682A00@xxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.17 (2007-11-01)

Scott's analysis is no doubt correct. But just on the off chance
that it is something simpler. I have been having all kinds of
wierdnesses on OSX 10.4.11 earlier today. Some web searching
indicated that people had similar problems a few years back
with OS Xafter doing a security update a few days before a timechange.
I tried rebooting in case some parts of my system hadn't got the
word about the time change. This fixed some of them. Still
tracing down others, but thought since your problems seemed
to start at the right time, that you might look into it.

HTH,
Paul

References:
- Re: Clock problems
  - From: Scott Bennett
- RE: Clock problems
  - From: downie -

Prev by Author: Re: 64 bit Linux
Next by Author: Re: MIT Circumvention Landscape Report
Previous by thread: RE: Clock problems
Next by thread: RE: Clock problems
Index(es):
- Author
- Thread