On 06/14/2016 06:40 AM, Richard Barmann wrote:
> About once a week when I boot up I find the clock is exactly 4 hours slow. I
> am using Kubuntu 16.04. If I am asking the question in the wrong place please
> send me to the correct forum.
> Thank you.
Try changing /etc/adjtime to have LOCAL at the
On Tuesday 14 June 2016 07:20:28 Jörg-Volker Peetz wrote:
> Richard Barmann wrote on 06/14/16 05:36:
> > About once a week when I boot up I find the clock is exactly 4 hours
> > slow. I am using Kubuntu 16.04. If I am asking the question in the wrong
> > place please send me to the correct forum.
>
On 6/14/16, Jörg-Volker Peetz wrote:
> Richard Barmann wrote on 06/14/16 05:36:
>> About once a week when I boot up I find the clock is exactly 4 hours slow.
>> I am
>> using Kubuntu 16.04. If I am asking the question in the wrong place please
>> send
>> me to the correct forum.
>> Thank you.
>>
>
Richard Barmann wrote on 06/14/16 05:36:
> About once a week when I boot up I find the clock is exactly 4 hours slow. I
> am
> using Kubuntu 16.04. If I am asking the question in the wrong place please
> send
> me to the correct forum.
> Thank you.
>
The four hours seem to be related to your ti
Richard Barmann composed on 2016-06-13 23:36 (UTC-0400):
About once a week when I boot up I find the clock is exactly 4 hours
slow. I am using Kubuntu 16.04. If I am asking the question in the wrong
place please send me to the correct forum.
Kubuntu is not Debian, but is heavily Debian based,
On Mon, Jun 13, 2016 at 11:36:59PM -0400, Richard Barmann wrote:
> About once a week when I boot up I find the clock is exactly 4 hours slow. I
> am using Kubuntu 16.04. If I am asking the question in the wrong place
> please send me to the correct forum.
> Thank you.
Kubuntu has its own community
On 2015-07-03 15:38:02 +0200, Michael Biebl wrote:
> In short, your ntp client should ensure that the clock is synced to RTC
> (google for "ntp 11 min mode sync" if you want to know more). For that
> we enable timesyncd by default in systemd.
Thanks for the information, but the documentation shoul
On Friday 03 July 2015 14:38:02 Michael Biebl wrote:
> Am 03.07.2015 um 15:18 schrieb Arno Schuring:
> >> Date: Fri, 3 Jul 2015 15:07:34 +0200
> >> From: vinc...@vinc17.net
> >>
> >> When I run "hwclock --systohc" manually before the reboot, the clock
> >> is OK after reboot. So, this seems to be a
> Date: Fri, 3 Jul 2015 15:38:02 +0200
> From: bi...@debian.org
>
> Am 03.07.2015 um 15:18 schrieb Arno Schuring:
>>
>>> Date: Fri, 3 Jul 2015 15:07:34 +0200
>>> From: vinc...@vinc17.net
>>>
>>> When I run "hwclock --systohc" manually before the reboot, the clock
>>> is OK after reboot. So, this
Am 03.07.2015 um 15:18 schrieb Arno Schuring:
>
>> Date: Fri, 3 Jul 2015 15:07:34 +0200
>> From: vinc...@vinc17.net
>>
>> When I run "hwclock --systohc" manually before the reboot, the clock
>> is OK after reboot. So, this seems to be a systemd bug. I've reported:
>>
>> https://bugs.debian.org/cgi
On Friday 03 July 2015 14:18:50 Arno Schuring wrote:
> > Date: Fri, 3 Jul 2015 15:07:34 +0200
> > From: vinc...@vinc17.net
> >
> > When I run "hwclock --systohc" manually before the reboot, the clock
> > is OK after reboot. So, this seems to be a systemd bug. I've reported:
> >
> > https://bugs.deb
> Date: Fri, 3 Jul 2015 15:07:34 +0200
> From: vinc...@vinc17.net
>
> When I run "hwclock --systohc" manually before the reboot, the clock
> is OK after reboot. So, this seems to be a systemd bug. I've reported:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790974
Michael, since I've seen
On 2015-07-01 02:24:14 +0200, Vincent Lefevre wrote:
> On 2015-06-30 18:15:18 -0400, Gary Dale wrote:
> > Is your cmos battery still providing power?
>
> The machine is new, so it should. The machine was also constantly on
> AC power.
>
> > Either that or your hardware clock could be broken or ve
On 2015-06-30 18:15:18 -0400, Gary Dale wrote:
> Is your cmos battery still providing power?
The machine is new, so it should. The machine was also constantly on
AC power.
> Either that or your hardware clock could be broken or very
> inaccurate.
If it loses 15 seconds just the time of a reboot,
On 30/06/15 05:52 PM, Vincent Lefevre wrote:
I've noticed that with my new HP ZBook G2, the clock loses time after
a reboot. Below is the openntpd log without the "peer" messages ("ntp
engine ready" means that this is just after a reboot). What is the
cause? Which part of the software is responsi
Daniel Melo
On Jan 24, 2013 11:33 PM, "Azuki" wrote:
> When I use linux-image-3.2.0-0.bpo.4-rt-amd64, An error of a large
> quantity of clock source occurs at the boot time when I connect
> usb-sound-card AS372(chip:CM6620).
> There is not the problem with the stability of the system, but these
Florian Kulzer wrote:
On Thu, Oct 19, 2006 at 17:21:39 +0200, steef wrote:
hi list,
maybe a stupid question, but nevertheless...
i have etch installed on one of my hd's, with a kde-desktop. like
allways i built this os from an absolute minimum of packages.
last night i tried to install
On Thu, Oct 19, 2006 at 17:21:39 +0200, steef wrote:
> hi list,
>
>
> maybe a stupid question, but nevertheless...
>
> i have etch installed on one of my hd's, with a kde-desktop. like
> allways i built this os from an absolute minimum of packages.
>
> last night i tried to install my hp-print
At Sun, 01 Oct 2006 20:05:03 +0200 Mathias Brodala said,
> Really on the desktop or only in the panel? ...
> If you want it on the desktop, maybe torsmo can help you.
OK; I got the panel back and it has a clock.
That is sufficient. Thanks,
... Peter E.
--
To UNSUBSCRIBE, ema
Hello Peter.
Peter Easthope, 01.10.2006 18:08:
> Etch is running here with kernel 2.6.16.
> Xfce is working; the desktop contains only
> the icons for Skype and for the terminal viewer.
>
> A small viewer on the desktop showing the
> date & time would be helpful.
Really on the desktop or only in
Thanks, that's what I needed to know.
Tyler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, 2006-09-28 at 08:53 -0400, Tyler Smith wrote:
> I'm having problems getting my clock to stay set. I'm dual booting with
> XP, and I can set the clock in XP and from the BIOS without problem.
> However, somewhere I've set Etch to consider the hardware clock as GMT,
> so I get a time three
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
Thanks for the suggestions. I tried noacpi as a kernel option and
adding in "toshiba" to /etc/modules, and my machine starts off at full
speed. So it doesn't appear to be any of those. I've installed
cpufreqd but it complains that I don't have a cpufreq interface in the
kernel - should I recompile,
David Hugh-Jones wrote:
> Hi
>
> I have an old Toshiba laptop (c 1999) which uses apm rather than the
> modern acpi. Whenever I boot up on battery power, the cpu speed is
> incorrectly detected as 48.175 MHz. This makes the system clock run
> way too fast, which means my time gets wrong, and also
On Thu, 12 May 2005, Glenn English wrote:
> The system clock on one of my machines is running way slow. If I
> repeatedly run 'date' the second changes once every 3 or 4 seconds.
> ntpdate will bring it into line, but ntpd can't keep it there.
are you using the same ntp server for ntpdate and n
Marty writes:
> I have not yet reported this as a bug.
It isn't a bug. You need to recompile your kernel with HZ defined as
something less than the default 1000.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On (13/05/05 00:04), Clive Menzies wrote:
> On (12/05/05 16:59), Glenn English wrote:
> > The system clock on one of my machines is running way slow. If I
> > repeatedly run 'date' the second changes once every 3 or 4 seconds.
> > ntpdate will bring it into line, but ntpd can't keep it there.
> >
Glenn English wrote:
The system clock on one of my machines is running way slow. If I
repeatedly run 'date' the second changes once every 3 or 4 seconds.
ntpdate will bring it into line, but ntpd can't keep it there.
I don't understand how this can happen. My experience with digital
electronics say
On Thursday 12 May 2005 23:59, Glenn English wrote:
> I don't understand how this can happen. My experience with digital
> electronics says that things almost never work half-way; they're fine,
> or they're dead. Anybody know what the system clock actually is? A
> counter counting the line frequenc
On (12/05/05 16:59), Glenn English wrote:
> The system clock on one of my machines is running way slow. If I
> repeatedly run 'date' the second changes once every 3 or 4 seconds.
> ntpdate will bring it into line, but ntpd can't keep it there.
>
> I don't understand how this can happen. My experie
On Tue, 23 Nov 2004 09:03:44 -0500, Robert Storey <[EMAIL PROTECTED]> wrote:
> On Mon, 22 Nov 2004 09:20:35 +
> Anthony Campbell <[EMAIL PROTECTED]> wrote:
>
> > On 22 Nov 2004, [EMAIL PROTECTED] wrote:
> > > I've been reading man pages of hwclock, xclock, adjtime, and so on,
> > > but cannot
On Mon, 22 Nov 2004 09:20:35 +
Anthony Campbell <[EMAIL PROTECTED]> wrote:
> On 22 Nov 2004, [EMAIL PROTECTED] wrote:
> > I've been reading man pages of hwclock, xclock, adjtime, and so on,
> > but cannot see how to adjust the time shown on teh icewm clock,
> > which is steadfastly 56 minutes
> On 22 Nov 2004, [EMAIL PROTECTED] wrote:
>> I've been reading man pages of hwclock, xclock, adjtime, and so on, but
>> cannot see how to adjust the time shown on teh icewm clock, which is
>> steadfastly 56 minutes ahead of the hwclock (which is set reasonably
>> correct). Which utility controls
On 22 Nov 2004, [EMAIL PROTECTED] wrote:
> I've been reading man pages of hwclock, xclock, adjtime, and so on, but
> cannot see how to adjust the time shown on teh icewm clock, which is
> steadfastly 56 minutes ahead of the hwclock (which is set reasonably
> correct). Which utility controls this?
On Mon, 22 Nov 2004 01:22:40 - (GMT), [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> I've been reading man pages of hwclock, xclock, adjtime, and so on, but
> cannot see how to adjust the time shown on teh icewm clock, which is
> steadfastly 56 minutes ahead of the hwclock (which is set reasona
Hi Richard
Have you tried booting up unplugged and seeing if that solves it? That
is the best workaround I have at the moment...
David
On Fri, 12 Nov 2004 13:14:48 +1300, Richard Hector
<[EMAIL PROTECTED]> wrote:
> On Thu, Nov 11, 2004 at 11:28:17AM +, David Hugh-Jones wrote:
>
>
> > Hi,
On Thu, Nov 11, 2004 at 11:28:17AM +, David Hugh-Jones wrote:
> Hi,
>
> I have a problem with kernel 2.6.8 on my Toshiba laptop. If I boot up
> with the power plugged in, the system clock runs much too fast - about
> 3 times too fast. I've been reading around this problem, and assume it
> has
on Fri, 27 Aug 2004 11:43:30AM -0400, Nori Heikkinen insinuated:
> on Fri, 27 Aug 2004 02:21:44PM +1000, Tim Connors insinuated:
> > Stefan O'Rear <[EMAIL PROTECTED]> said on Thu, 26 Aug 2004 20:34:17 -0700:
> > > On Thu, Aug 26, 2004 at 11:23:07PM -0400, Nori Heikkinen wrote:
> > > > over the past
On Fri, 27 Aug 2004, Nori Heikkinen wrote:
> on Fri, 27 Aug 2004 02:21:44PM +1000, Tim Connors insinuated:
> > Stefan O'Rear <[EMAIL PROTECTED]> said on Thu, 26 Aug 2004 20:34:17 -0700:
> > > On Thu, Aug 26, 2004 at 11:23:07PM -0400, Nori Heikkinen wrote:
> > > > over the past few days, i've notic
on Fri, 27 Aug 2004 02:21:44PM +1000, Tim Connors insinuated:
> Stefan O'Rear <[EMAIL PROTECTED]> said on Thu, 26 Aug 2004 20:34:17 -0700:
> > On Thu, Aug 26, 2004 at 11:23:07PM -0400, Nori Heikkinen wrote:
> > > over the past few days, i've noticed that my system clock gets about
> > > ten to fift
on Thu, 26 Aug 2004 08:34:17PM -0700, Stefan O'Rear insinuated:
> On Thu, Aug 26, 2004 at 11:23:07PM -0400, Nori Heikkinen wrote:
> > over the past few days, i've noticed that my system clock gets about
> > ten to fifteen minutes slow over the course of a day. this is really
> > weird! i've been
on Fri, 27 Aug 2004 09:27:48AM -0400, Loki insinuated:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 26 Aug 2004, Nori Heikkinen wrote:
>
> > i want my system to ALWAYS be on time.
>
> you're close with ntpdate
>
> apt-get install ntp
>
> it uses more system resources, but it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 26 Aug 2004, Nori Heikkinen wrote:
> i want my system to ALWAYS be on time.
you're close with ntpdate
apt-get install ntp
it uses more system resources, but it's usually worth it. i only use
ntpdate on my ancient 486 laptop.
- --
GnuPG pub
Stefan O'Rear <[EMAIL PROTECTED]> said on Thu, 26 Aug 2004 20:34:17 -0700:
> On Thu, Aug 26, 2004 at 11:23:07PM -0400, Nori Heikkinen wrote:
> > over the past few days, i've noticed that my system clock gets about
> > ten to fifteen minutes slow over the course of a day. this is really
> > weird!
On Thu, Aug 26, 2004 at 11:23:07PM -0400, Nori Heikkinen wrote:
> over the past few days, i've noticed that my system clock gets about
> ten to fifteen minutes slow over the course of a day. this is really
> weird! i've been using ntpdate to synchronize it with a timeserver
> whenever i notice it
On Sat, 07 Aug 2004 13:21:55 -0400, Dougpol1 wrote:
> My clock is about 4hours off. how can I resett it??
Hi, Doug:
Check your timezone. I'm sure you've configured the wrong one.
The other reason might be that you set the real time clock to using
universal time, not local time.
I'm new
On Sat, 07 Aug 2004 13:21:55 -0400
Dougpol1 <[EMAIL PROTECTED]> wrote:
> Hello,
> My clock is about 4hours off. how can I resett it??
hwclock --set --date="08/07/2004 18:00:00" should do it for you.
"man hwclock" for more information.
HTH,
Jacob
--
GnuPG Key: 1024D/16377135
Random .sign
On 08/05/04 14:10, Antonio Rodriguez wrote:
I am thinking about implementing the sounds of an old town tower clock
in my machine. With cron is not a big deal (the only complication that
I can see now would be the amount of strikes according to the hour),
so I wonder if someone would recommend sound
* Person Rus Foster <[EMAIL PROTECTED]> wrote:
> Hi All,
> I'm running 2.4.20 and just noticed the following
[...]
> Warning: time of day goes back (-2350140us), taking countermeasures.
> Warning: time of day goes back (-2349258us), taking countermeasures.
> 64 bytes from gkar.fsck.me.uk (198.78.
also sprach Bill Moseley <[EMAIL PROTECTED]> [2002.12.05.0616 +0100]:
> This is on an old Dell PIII machine.
Speaking from experience, Dell PCs seem to be unable to keep the time
with any other operating system than Windoze. Do you have things like
Intel SpeedStep enabled in the BIOS?
I am using
A, the mist clears. That may be the source of my troubles some time back.
NTP _had_ been working flawlessly for many years, then all of a sudden it
stoped working properly on both of my machines. Exact symptoms that Bill is
describing.
Thinking back I had started using the ide-scsi on b
On Thu, 5 Dec 2002, Kent West wrote:
> Bill Moseley wrote:
>
> >I setup a machine for a friend and every few days I ssh in to see how
> >things look. Twice now I have found the date about twenty minutes behind.
> >
> >This is on an old Dell PIII machine.
> >
> >
>
>
> Weak CMOS battery?
No
Bill Moseley wrote:
I setup a machine for a friend and every few days I ssh in to see how
things look. Twice now I have found the date about twenty minutes behind.
This is on an old Dell PIII machine.
Weak CMOS battery?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
[EMAIL PROTECTED] said:
> I also saw this problem on a suite of machines that were being used
> for distributed performance testing. We had xntpd running but the
> clocks still lost too much accuracy too quickly. We ended up setting
> up a process that automatically ran ntpdate every 10 seconds
tracked down the cause though.
-Original Message-
From: Bill Moseley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 04, 2002 11:19 PM
To: James Tappin; [EMAIL PROTECTED]
Subject: Re: Clock running slow
At 07:03 AM 12/05/02 +, James Tappin wrote:
>Does the machine have a S
At 07:03 AM 12/05/02 +, James Tappin wrote:
>Does the machine have a SCSI bus or a device running under ide-scsi? I
>have seen clocks run extremely slow (less than half speed) when using SCSI
>devices with disconnects disabled. NTP can fail to correct if the shift is
>too big.
Yes it does. Th
On Wed, 04 Dec 2002 21:16:23 -0800
Bill Moseley <[EMAIL PROTECTED]> wrote:
> I setup a machine for a friend and every few days I ssh in to see how
> things look. Twice now I have found the date about twenty minutes
> behind.
Does the machine have a SCSI bus or a device running under ide-scsi? I
At 04:51 PM 12/05/02 +1100, David Cureton wrote:
>I had this problem also, never really put my finger on what was causing it,
>however I have a feeling that is was due to the NTP server being a different
>NTP version.
>Running ntpdc utility:
> entering in the 'sysstats' command and observi
Bill Moseley wrote:
I setup a machine for a friend and every few days I ssh in to see how
things look. Twice now I have found the date about twenty minutes behind.
The first time I found this I ran ntpdate, made sure the hwclock was
updated, restarted ntp-simple and thought the problem was fixed.
hey guys,
out of curiosity, do you have errors in your /var/log/messages or syslog
about a missing char-major-10-135? i had the same problem on my machine
a while back because i didn't have rtc support in my kernel. just an
idea anyways. also, are you sure that you're connecting to the time
ser
I had this problem also, never really put my finger on what was causing it,
however I have a feeling that is was due to the NTP server being a different
NTP version.
Whilst there was nothing in the logs about this, the clue that lead me to
being different versions was that:
Running ntpdc util
Tom Schuetz wrote:
>
> Using xf86config, when I run the autoprobe for a clock chip line, the screen
> blanks, then comes back with an 'autoprobe call failed' error line.
Why? Do you know for a fact that you need a clockchip setting? If you
don't know this for a fact, you should NOT be probing
its possible that the hardware clock is off, run 'hwclock' to see what
it says, if it is different from the 'date' command you can run 'hwclock
--systohc' to synch them.
nate
Frederik wrote:
>
> Hi,
>
> I've a strange problem: my clock is displaying an incorrect time since
> today (I had an X c
Frederik said:
> I've a strange problem: my clock is displaying an incorrect time since
> today (I had an X crash this morning, followed by a reboot).
> The time now on my machine is 18:43, although it's 17:31. This makes me
> believe it's not timezone-related...
> I have the package ntp installed,
On Mon, 1999-11-29 at 15:28:57 -0600, Marc Mongeon wrote:
> I think this is caused by the file /etc/adjtime, which is supposed to
> adjust for clock drift, but gets skewed when you first set the hard-
> ware clock. Remove the file, then re-set the clock. It will be re-
> created as needed.
>
>
I think this is caused by the file /etc/adjtime, which is supposed to
adjust for clock drift, but gets skewed when you first set the hard-
ware clock. Remove the file, then re-set the clock. It will be re-
created as needed.
Marc
--
Marc Mongeon <[EMAIL PROTECTED]>
Unix Specialist
Ban-K
aphro writes:
> ...xntp3 might update the clock automatically...
Yes. So does chrony.
--
John HaslerThis posting is in the public domain.
[EMAIL PROTECTED]Do with it what you will.
Dancing Horse Hill Make money from it if you can; I don't mind.
Elmwood, Wisco
On Tue, 9 Nov 1999, Jean-Yves BARBIER wrote:
jybarb >Do you have a clue to use the log files from xntp3 to correctly
jybarb >setup time TICK & FREQ, in order to have quite a good time
jybarb >kept by the cmos clock on a machine which only works a few
jybarb >hours a day?
jybarb >
no sorry, i
On Mon, Nov 08, 1999 at 12:50:10PM -0800, aphro wrote:
>.
> my
> server's clock is never off by more then 0.01 seconds.
>
> nate
Hi nate,
Do you have a clue to use the log files from xntp3 to correctly
setup time TICK & FREQ, in order to have quite a good time
kept by the cmos clock on a
On Mon, 8 Nov 1999, Robert Kerr wrote:
kerrr >Okay, so what do we do if the system time loses time when the computer is
kerrr >on? The hwclock is fine, but the system time keeps losing it.
kerrr >Thanks
run a cron job for ntpdate, have it run every 30 mins, or every 60
mins..or every minute..xnt
On Wed, 27 Oct 1999, Martin Fluch wrote:
> On Wed, 27 Oct 1999, Robert Kerr wrote:
>
> > Hi all,
> > Whenever I boot to debian, my computer's clock gets set to some other
> > time. This morning I turned it on and all of a sudden it told me it was
> > three hours and 45 minutes earlier than my al
On 27 Oct 1999, Salman Ahmed wrote:
> > "AC" == Anthony Campbell <[EMAIL PROTECTED]> writes:
> AC> Have you got APM compiled in the kernel? I was getting this problem
> AC> and it took me several days to find out that APM was resetting the
> AC> time (and date).
>
> I have the foll
On 27 Oct 1999, Robert Kerr wrote:
> Hi all,
> Whenever I boot to debian, my computer's clock gets set to some other
> time. This morning I turned it on and all of a sudden it told me it was
> three hours and 45 minutes earlier than my alarm clock said. I almost
> went back to bed. Anyway, the o
did u set the clock in the bios after u installed the MB ??
nate
[mailto:[EMAIL PROTECTED] ]--
Vice President Network Operations http://www.firetrail.com/
Firetrail Internet Services Limited http://www.aphroland.org/
Everett, WA 425-3
On Wed, 27 Oct 1999, Robert Kerr wrote:
> Hi all,
> Whenever I boot to debian, my computer's clock gets set to some other
> time. This morning I turned it on and all of a sudden it told me it was
> three hours and 45 minutes earlier than my alarm clock said. I almost
> went back to bed. Anyway,
David Kanter wrote:
> Is there a way to sync the time with a server when I start a PPP, so I
> won't have to worry about this in the future? I vaguely remember a
> mention of this when installing Slink.
Take a look at chrony. It does everything xntp does and its default
configuration works fine w
On Tue, Oct 05, 1999 at 04:17:18PM +0200, Stephan Engelke wrote:
> Hi David,
>
> On Tue, Oct 05, 1999 at 09:07:02AM -0500, David Kanter wrote:
>
> > Is there a way to sync the time with a server when I start a PPP, so I
> > won't have to worry about this in the future? I vaguely remember a ment
On Tue, Oct 05, 1999 at 10:35:13AM -0500, Dave Sherohman wrote:
> Stephan Engelke said:
> > Check xntp and ntpdate. I believe there is a .deb-package called xntp.
> > Next place a call to "ntpdate " in your ip-up.d.
>
> Not to steal another Dave's question, but...
>
> Where can one find a list o
*- On 5 Oct, Dave Sherohman wrote about "Re: Clock is loosing time"
> Stephan Engelke said:
>> Check xntp and ntpdate. I believe there is a .deb-package called xntp.
>> Next place a call to "ntpdate " in your ip-up.d.
>
> Not to steal another Dave
Stephan Engelke said:
> Check xntp and ntpdate. I believe there is a .deb-package called xntp.
> Next place a call to "ntpdate " in your ip-up.d.
Not to steal another Dave's question, but...
Where can one find a list of publicly-usable NTP servers?
Hi David,
On Tue, Oct 05, 1999 at 09:07:02AM -0500, David Kanter wrote:
> Is there a way to sync the time with a server when I start a PPP, so I won't
> have to worry about this in the future? I vaguely remember a mention of this
> when installing Slink.
Check xntp and ntpdate. I believe the
[Please use <76 character lines]
On Tue, Oct 05, 1999 at 09:07:02 -0500, David Kanter wrote:
> Why is the time as shown by asclock drifting so far from the real time?
> Does Linux read the BIOS time, and therefore my BIOS clock is losing time
> quickly,
Could be; see clock(8).
> or is something
Subject: Re: clock
Date: Fri, May 14, 1999 at 10:43:23PM +0100
In reply to:Patrick Kirk
Quoting Patrick Kirk([EMAIL PROTECTED]):
> What is the man page for info on setting the clock to salmon.maths.tcd.ie
> which is a time server near a lovely pub in Dublin?
>
> i live in ireland, i'm running a potato system, and it kicks ass, except
> 'date' tells me the wrong time. /etc/timezone says Eire, which is correct.
> i'm in the GMT timezone. i want the CMOS clock, and the software clock to
> be set to GMT. how do i do this?
Look for a file called /etc/def
What is the man page for info on setting the clock to salmon.maths.tcd.ie which
is a time server near a lovely pub in Dublin?
Patrick
On Fri, May 14, 1999 at 03:52:46PM -0400, Wayne Topa wrote:
>
> Subject: clock
> Date: Fri, May 14, 1999 at 05:03:52PM +0100
>
> In reply to:Vincent
Subject: clock
Date: Fri, May 14, 1999 at 05:03:52PM +0100
In reply to:Vincent Murphy
Quoting Vincent Murphy([EMAIL PROTECTED]):
> i live in ireland, i'm running a potato system, and it kicks ass, except
> 'date' tells me the wrong time. /etc/timezone says Eire, which is correc
Tun,
> Hi... while compiling the kernel, I got a "Clock Skew detected, your
> compile may not be complete" (or something to that effect...)
> What is clock skew?
It's probably due to the fact that you have modification time of
files in the future! That is only possible if you had a bad ti
On Tue, Jan 13, 1998 at 01:10:47PM +0100, Jens Ch. Lisner wrote:
> I've got a strange warning after "make menuconfig" with
> kernel-source-2.0.34. It says "clock skew detected". I don't know what it
> means. Can you help?
Is your kernel source located on an NFS mount? If the NFS server's clock
is
On Tue, 13 Jan 1998 13:10:47 +0100 (CET), you scribbled:
>
>Hi all,
>
>I've got a strange warning after "make menuconfig" with
>kernel-source-2.0.34. It says "clock skew detected". I don't know what it
>means. Can you help?
Your post seems to think it was done in January :-) I would suggest check
1 - 100 of 126 matches
Mail list logo
