On Monday 15 June 2009 08:20:23 debian-user-digest-requ...@lists.debian.org
wrote:
> > Even more. I get a bootup error message failing to set date (and time)
> > to ... the following day + 3 hours!!
>
> You may have a bad system clock. That does happen on some older
> hardware or if a CMOS battery
On Sun, Jun 14, 2009 at 04:50:23PM +0300, David Baron wrote:
> Even more. I get a bootup error message failing to set date (and time)
> to ... the following day + 3 hours!!
You may have a bad system clock. That does happen on some older
hardware or if a CMOS battery goes bad. I'd do the following
>>>Has been happening quite a bit lately:
>>>Problem with ntpdate. If and when it finally works, get a change of 10,800
>seconds ... that is 30 minutes.
>>>The dovecot IMAPd server is unreadable. Restarting it yields a complaint
>>>about 10,800 seconds of time, killing itself now! Restarting it
On Thu, Jun 11, 2009 at 04:08:54PM +0300, David Baron wrote:
> >>Has been happening quite a bit lately:
>
> >>Problem with ntpdate. If and when it finally works, get a change of 10,800
> >seconds ... that is 30 minutes.
>
> >>The dovecot IMAPd server is unreadable. Restarting it yields a complai
On Thu,11.Jun.09, 16:08:54, David Baron wrote:
> OK, time to fix this. Since my system comes up with the "correct" time zone
> but three hours later, it must be interpreting the stored (hw) time as GMT
> and
> adding the three hours (gmt+2 + daylight savings).
>
> How to fix this?
If you onl
>>Has been happening quite a bit lately:
>>Problem with ntpdate. If and when it finally works, get a change of 10,800
>seconds ... that is 30 minutes.
>>The dovecot IMAPd server is unreadable. Restarting it yields a complaint
>>about 10,800 seconds of time, killing itself now! Restarting it agai
>Has been happening quite a bit lately:
>Problem with ntpdate. If and when it finally works, get a change of 10,800
>seconds ... that is 30 minutes.
>The dovecot IMAPd server is unreadable. Restarting it yields a complaint
>about 10,800 seconds of time, killing itself now! Restarting it again
>w
The current chrony initscript looks for a defaultroute at startup. If one
is found it puts chronyd online. The ip-up script is only used with PPP.
--
John Hasler
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@list
On Sun, 7 Jun 2009 10:59:50 -0400
Daryl Styrk wrote:
...
> I've had nothing but great results with chrony. Aside from an issue of
> chrony falling back to 127.127.1.1 when it cannot connect to a ntp server..
> Which happens often with my laptop as I move around during the day.. I
> fixed tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jun 07, 2009 at 05:07:08PM +0300, David Baron wrote:
> Has been happening quite a bit lately:
>
> Problem with ntpdate. If and when it finally works, get a change of 10,800
> seconds ... that is 30 minutes.
>
> The dovecot IMAPd server is un
Has been happening quite a bit lately:
Problem with ntpdate. If and when it finally works, get a change of 10,800
seconds ... that is 30 minutes.
The dovecot IMAPd server is unreadable. Restarting it yields a complaint about
10,800 seconds of time, killing itself now! Restarting it again works
11 matches
Mail list logo
