begin quote
On Thu, 3 Jul 2003 21:34:12 +0200 (CEST)
Joel Palmius <[EMAIL PROTECTED]> wrote:
> As a note of interest here: I don't think this is gentoo-specific
> problem. I had exactly the same problem with two different versions of
> Mandrake too.
>
> Amusingly enough I never had the problem
On Fri, Jul 04, 2003 at 11:42:59AM +0200, Joel Palmius wrote:
> Although, what to do when it seems it is the system *software* that seems
> to mess up time and there seems to be no explanation as to why?
>
> These are the explanations I've heard so far for the lagging time
> behavior:
>
> [...]
William Kenworthy <[EMAIL PROTECTED]> wrote:
> There is more than one cause. Check the forums, its full of this
> issue. The definite cause for me on a celery dell laptop was the gnome
> battery applet. It has a known bug (fixed???) where it stalls the
> machine whilst reading /proc under apm.
>
There is more than one cause. Check the forums, its full of this
issue. The definite cause for me on a celery dell laptop was the gnome
battery applet. It has a known bug (fixed???) where it stalls the
machine whilst reading /proc under apm.
On a later machine with a much faster p4, you can som
On Fri, 4 Jul 2003, Robert Bragg wrote:
> My point was (I still think this is correct) that if his setup is
> resulting in his clock getting out of sync on a daily basis, by 20-30
> minutes then he has bigger problems to think about before he starts
> playing with ntpd.
True, true.. I stopped us
On Thu, Jul 03, 2003 at 10:20:32PM +, Juri Haberland wrote:
> Robert Bragg <[EMAIL PROTECTED]> wrote:
> > I think ntp is the wrong tool for the job here. ntp isn't for keeping you
> > clock about right, its for when you want yor clock to be extremly acurate.
>
> > Just saying, 'coz ntpd seems
Juri Haberland <[EMAIL PROTECTED]> wrote:
Whoops, lots of spelling mistakes.
Sorry for that.
Cheers,
Juri
--
Juri Haberland <[EMAIL PROTECTED]>
--
[EMAIL PROTECTED] mailing list
Stroller <[EMAIL PROTECTED]> wrote:
> On 3/7/03 6:28 pm, "Christopher Egner" <[EMAIL PROTECTED]> wrote:
>
>> Alright then, any ideas what to use. I mean, I agree syncing to multiple
>> servers seems a bit drastic (nice to know I won't be late for work, but
>> still...). ...
It's not drastic. It's
On Thu, 2003-07-03 at 17:23, Stroller wrote:
> On 3/7/03 6:28 pm, "Christopher Egner" <[EMAIL PROTECTED]> wrote:
>
> > Alright then, any ideas what to use. I mean, I agree syncing to multiple
> > servers seems a bit drastic (nice to know I won't be late for work, but
> > still...). ...
> >
> > If
Robert Bragg <[EMAIL PROTECTED]> wrote:
> I think ntp is the wrong tool for the job here. ntp isn't for keeping you
> clock about right, its for when you want yor clock to be extremly acurate.
> Just saying, 'coz ntpd seems to be a slightly missused tool.
Nope, ntp is *exactly* for keeping your
On 3/7/03 6:28 pm, "Christopher Egner" <[EMAIL PROTECTED]> wrote:
> Alright then, any ideas what to use. I mean, I agree syncing to multiple
> servers seems a bit drastic (nice to know I won't be late for work, but
> still...). ...
>
> If anyone has any other ideas. let me know
rdate was mention
As a note of interest here: I don't think this is gentoo-specific problem.
I had exactly the same problem with two different versions of Mandrake
too.
Amusingly enough I never had the problem with older versions of Mandrake,
so something must've changed during the last 18 months or so.
(this
Alright then, any ideas what to use. I mean, I agree syncing to multiple
servers seems a bit drastic (nice to know I won't be late for work, but
still...). Shoot even syncing to one! I saw the perl script, and I'll
give that a go, but there's gotta be a better way. I mean for the system
to be off t
I think ntp is the wrong tool for the job here. ntp isn't for keeping you
clock about right, its for when you want yor clock to be extremly acurate.
You should have a working clock to startwith (i.e. no harware errors or
miss-configurations) Unless you force it to (-g I think), ntpd will usually
I have this problem too, but noticed that there's a difference between
system time (as measured by "date") and hardware time (as measured by
"hwclock"). Since the hardware clock seemed to keep up, while the system
time sometimes lagged as much as 25% compared to real time, my solution
was to ma
Nevermind. Stupid me didn't set the timezone in KDE to view! Well now
I'm gonna go kick myself. Night
--
Christopher
In 1968 it took the computing power of 2 C-64's to fly a rocket to the
moon. Now, in 1998 it takes the Power of a Pentium 200 to run Microsoft
Windows 95. Something must have gone
Alright, perhaps I'm a bit lost on this. My clock always runs off about
20 to 30 minutes after a day or so. Only in linux though. I figured I'd
start using ntpd. However, I can't seem to figure out how to configure a
timezone for it. Any help here would be great.
--
Christopher
In 1968 it took th
17 matches
Mail list logo
