On Sunday 19 February 2006 18:26, Mirko Parthey wrote:
> On Sat, Feb 18, 2006 at 10:53:09PM +0200, David Baron wrote:
>>> Ntpdate is what I am using. Maybe the setup needs be changed.
>>
>> Which timeservers are you getting the time from? (see /etc/default/ntpdate)
>> Do they provide the correct ti
On Sunday 19 February 2006 18:26, Mirko Parthey wrote:
> On Sat, Feb 18, 2006 at 10:53:09PM +0200, David Baron wrote:
> > Ntpdate is what I am using. Maybe the setup needs be changed.
>
> Which timeservers are you getting the time from? (see /etc/default/ntpdate)
> Do they provide the correct time?
On Sat, Feb 18, 2006 at 10:53:09PM +0200, David Baron wrote:
> Ntpdate is what I am using. Maybe the setup needs be changed.
Which timeservers are you getting the time from? (see /etc/default/ntpdate)
Do they provide the correct time?
Try "/etc/init.d/ntpdate start", and look in /var/log/syslog f
On Friday 17 February 2006 23:12, Mirko Parthey wrote:
> On Thu, Feb 16, 2006 at 05:27:50PM +0200, David Baron wrote:
> > Every few days, I find my clock two hours fast. Easy enough to reset but
> > ... why?
> >
> > I am running 2.6.15 kernel, Sid, and time is updated using ntp. Since my
> > time z
> > Every few days, I find my clock two hours fast. Easy enough to reset but
> > ... why?
> >
> > I am running 2.6.15 kernel, Sid, and time is updated using ntp. Since my
> > time zone is universal + two hours, maybe the two hours means something.
>
> Make sure you have your timezone correctly conf
On Thu, Feb 16, 2006 at 05:27:50PM +0200, David Baron wrote:
> Every few days, I find my clock two hours fast. Easy enough to reset but ...
> why?
>
> I am running 2.6.15 kernel, Sid, and time is updated using ntp. Since my time
> zone is universal + two hours, maybe the two hours means somethin
just follow this http://www.debianhelp.co.uk/time.htm and in this article menctioned that try to install ntpdate packageMarty <[EMAIL PROTECTED]> wrote: David Baron wrote:> Every few days, I find my clock two hours fast. Easy enough to reset but ... > why?> > I am running 2.6.15 kernel, Sid, and t
David Baron wrote:
Every few days, I find my clock two hours fast. Easy enough to reset but ...
why?
I am running 2.6.15 kernel, Sid, and time is updated using ntp. Since my time
zone is universal + two hours, maybe the two hours means something. Bug?
This can happen if you use UTC in your R
David Baron schreef:
Every few days, I find my clock two hours fast. Easy enough to reset but ...
why?
I am running 2.6.15 kernel, Sid, and time is updated using ntp. Since my time
zone is universal + two hours, maybe the two hours means something. Bug?
Apart from time zone problems, it just
David Baron writes:
> Every few days, I find my clock two hours fast. Easy enough to reset but ...
> why?
> I am running 2.6.15 kernel, Sid, and time is updated using ntp. Since my
> time zone is universal + two hours, maybe the two hours means something.
Make sure you have your timezone correct
David;
This may not be the case, BUT there are several m/b's (I have an older abit
BX6 rev) that I understand can cause the pc clock to be skew under Win98.
It does with the box I built. Could be a similar effect.
>Every few days, I find my clock two hours fast. Easy enough to reset but ...
>w
Every few days, I find my clock two hours fast. Easy enough to reset but ...
why?
I am running 2.6.15 kernel, Sid, and time is updated using ntp. Since my time
zone is universal + two hours, maybe the two hours means something. Bug?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
12 matches
Mail list logo
