Hi,
On Sat, 2009-05-16 at 09:07 +0800, Umarzuki Mochlis wrote:
> Using: Lenny i386
>
> The only way I can bypass this is to go "single user mode" and
> pressing Ctrl+d, any other way to get rid of this problem?
I suspect it's a problem specific to your RTC clock. What's your
hardware (or motherb
Using: Lenny i386
The only way I can bypass this is to go "single user mode" and pressing
Ctrl+d, any other way to get rid of this problem?
--
Regards,
Umarzuki Mochlis
http://gameornot.net
system time
> all by itself (although you may want to test for it first: look for this in
> /var/log/dmesg: "setting system clock to").
Yes, right. Thanks for the tip.
Girish.
--
Girish Kulkarni - Allahabad, India - http://girish.50webs.com
--
To UNSUBSCRIBE, email to [EMAIL P
On Mon, 08 Sep 2008, Andrei Popescu wrote:
> On Mon,08.Sep.08, 11:55:24, Henrique de Moraes Holschuh wrote:
>
> [...]
>
> > It gets better. If your RTC is in UTC, you can remove the initscript calls
> > for hwclock in the S runlevel, and get a marginally faster boot, too.
>
> I have two scripts
Can
I disable both?
> Recent kernels know how to read a RTC in UTC and set the initial system time
> all by itself (although you may want to test for it first: look for this in
> /var/log/dmesg: "setting system clock to").
Yep, got it.
Regards,
Andrei
--
If you can'
level, and get a marginally faster boot, too.
Recent kernels know how to read a RTC in UTC and set the initial system time
all by itself (although you may want to test for it first: look for this in
/var/log/dmesg: "setting system clock to").
--
"One disk to rule them all, One d
On Du,07.sep.08, 21:18:30, Girish Kulkarni wrote:
> On Sun, Sep 7, 2008 at 9:04 PM, Andrei Popescu wrote:
> > You mean the BIOS shows the correct *local* time? In case you don't run
> > Windows on the same machine you should set it to UTC and let Debian
> > handle the time difference. Just make sur
On Sun, Sep 7, 2008 at 9:04 PM, Andrei Popescu wrote:
> You mean the BIOS shows the correct *local* time? In case you don't run
> Windows on the same machine you should set it to UTC and let Debian
> handle the time difference. Just make sure you have the right time zone
> by running 'dpkg-reconfig
On Sun,07.Sep.08, 20:41:23, Girish Kulkarni wrote:
> I installed Debian 4.0 on my laptop this Thursday. And I notice today
> that the system clock is running faster by 0530 hours. My BIOS shows
> the correct time, but Debian changes to this advanced time at every
> reboot. What co
Am 07.09.2008 um 17:11 schrieb Girish Kulkarni:
I installed Debian 4.0 on my laptop this Thursday. And I notice today
that the system clock is running faster by 0530 hours. My BIOS shows
the correct time, but Debian changes to this advanced time at every
reboot. What could be going wrong
I installed Debian 4.0 on my laptop this Thursday. And I notice today
that the system clock is running faster by 0530 hours. My BIOS shows
the correct time, but Debian changes to this advanced time at every
reboot. What could be going wrong? (Interestingly, I use the Indian
Standard Time, which
On 27/10/2007 Russell L. Harris wrote:
> Has it been more than three or four years since you changed the CMOS
> RAM backup battery on the motherboard? A dead battery can cause
> difficulties, because some of the time utilities expect to make only
> minor corrections (seconds and minutes, not month
On Oct 27, 2007, at 10:22 AM, Russell L. Harris wrote:
* Jonas Meurer <[EMAIL PROTECTED]> [071027 09:14]:
i remember some debconf question at the installation of debian,
where i
was asked whether my hardware clock is set to GMT. is GMT the same
as UTC?
and to which package does this ques
* Jonas Meurer <[EMAIL PROTECTED]> [071027 09:14]:
> hello,
>
> since one or two months, my system clock is reset on every reboot.
>
> # date
> Sun Oct 28 11:37:15 CET 2007
> # ntpdate-debian
> 27 Oct 15:52:03 ntpdate[14642]: step time server 134.34.3.19 offset
&
hello,
since one or two months, my system clock is reset on every reboot.
# date
Sun Oct 28 11:37:15 CET 2007
# ntpdate-debian
27 Oct 15:52:03 ntpdate[14642]: step time server 134.34.3.19 offset
-74779.179229 sec
if i'm correct, this is due to a wrongly set hardware clock. so i se
Dario Rossi napisał(a):
Hello,
i have a etch installation, daily updated.
I am experiencing a problem with system clock infact it "suddenly"
started running at half speed ( means that if i run "sleep 2", it takes
more or less 4 seconds to complete).
I recompiled the kern
Hello,
i have a etch installation, daily updated.
I am experiencing a problem with system clock infact it "suddenly"
started running at half speed ( means that if i run "sleep 2", it takes
more or less 4 seconds to complete).
I recompiled the kernel upgrading it from 2.6.1
On Fri, Nov 10, 2006 at 08:35:36AM -0500, Louis-David Perron wrote:
> David Hart wrote:
> > Disabling APM cured the symptoms.
>
> Up to now, it seems to work perfectly! I guess that this IBM desktop machine
> has some similarities with a laptop.
Thanks for your reply and I'm glad it seems to ha
On Thu, Nov 09, 2006 at 10:08:58AM -0500, Louis-David Perron wrote:
> Since I upgraded this server to the 2.6 kernel branch, I have this,
> weird, and HEAVY system clock problem. This machine was running
> perfectly using a 2.4 kernel. In less than 24 hours, the system clock
>
This is a resend... I think my first e-mail didn't go through.
Since I upgraded this server to the 2.6 kernel branch, I have this,
weird, and HEAVY system clock problem. This machine was running
perfectly using a 2.4 kernel. In less than 24 hours, the system clock
seems to get stuck
On Mon, 06 Nov 2006 21:33 +0100 Franck PASSELEGUE wrote:
> I don't understand why the time (given by date() commande) is
> completly false.
> The drift of the system clock is about 10min after 2 hours !!
Over the years I have seen this happen a few times. The last time was
when I
On Mon, 2006-11-06 at 21:33 +0100, Franck PASSELEGUE wrote:
> Hello,
>
> I'm running Debian sarge Rc3 on a new computer. An Intel celeron 3Ghz.
> I don't understand why the time (given by date() commande) is completly
> false.
> The drift of the system clock i
Hello,
I'm running Debian sarge Rc3 on a new computer. An Intel celeron 3Ghz.
I don't understand why the time (given by date() commande) is completly
false.
The drift of the system clock is about 10min after 2 hours !!
I tried to start my computer from a live Cd (ubuntu 6.10) an
On Sun, May 01, 2005 at 08:03:37PM +0200, Roel Schroeven wrote:
> I'm afraid I can't help you (though my suggestion of trying chrony still
> stands).
I should have been more clear, but as I said in the first part of my
response, I did install chrony, and it solved the problem. The second
part of
Arjen Meek wrote:
On Sat, Apr 30, 2005 at 05:32:28PM +0200, Roel Schroeven wrote:
In my experience, chrony does a better job of coping with clocks that
run very fast or very slow.
Thanks for the tip. I replaced ntpd with chrony on the system in
question, and after setting it up properly and doing
On Sat, Apr 30, 2005 at 05:32:28PM +0200, Roel Schroeven wrote:
> In my experience, chrony does a better job of coping with clocks that
> run very fast or very slow.
Thanks for the tip. I replaced ntpd with chrony on the system in
question, and after setting it up properly and doing a "makestep"
I also recommend Chrony. You might need to configure it slightly, but
it works quite well.
jens <[EMAIL PROTECTED]> wrote:
> Thanks for your reply Chris. Ok, I confess, I stuck an extra 'n' in there
> me bad.
Why, oh why, oh why, did you email me as well as replying here? If
someone answers your post then surely it's obvious they're reading the
newsgroup/mailing list, so you don't
On Wed, 22 Dec 2004 20:45:55 +, jens wrote:
> Hi there, I set up a new Debian box with a 2.6 kernel. For some reason or
> other I can't get the system time to be correct. When I do a 'tzconfig' it
> reports me as being in the correct time zone (American/Vancouver) but
> when I do a 'date' comma
On a machine we recently installed (testing) we have this problem at boot
Hang up on synchronising system clock to hardware clock
Then if you Ctrl + C the boot procedure goes ahead. It stops again with the
same message. If you Ctrl + C again, the boot procedure goes ahead
successfully and
On Tue, Jun 22, 2004 at 04:42:27PM +0200, Felix C. Stegerman wrote:
> Now, my system clock is running too fast: about 3-4x normal speed.
> This is obviously not very convenient.
Specially because this will make you age 3-4x faster. You'll lose your youth
in a snap. Hey, at least your
On 22 Jun 2004, Felix C. Stegerman wrote:
> Anthony Campbell wrote:
> >On 22 Jun 2004, Felix C. Stegerman wrote:
>
> >>I realise this is probably not Debian-specific,
> >>but I'm hoping someone on this list can help me out anyway.
>
> [...]
>
> >I found the clock was fast (though not as fast as
Anthony Campbell wrote:
On 22 Jun 2004, Felix C. Stegerman wrote:
I realise this is probably not Debian-specific,
but I'm hoping someone on this list can help me out anyway.
[...]
I found the clock was fast (though not as fast as that) with kernel
2.6.6. It also was very difficult to regulate with
Felix C. Stegerman wrote:
Stefano Rivoir wrote:
Felix C. Stegerman wrote:
I realise this is probably not Debian-specific,
but I'm hoping someone on this list can help me out anyway.
[...]
It's a known problem, both in early -bk and in -mm1. Either wait for
-mm2 or look for the right fix, it's be
On 22 Jun 2004, Felix C. Stegerman wrote:
> I realise this is probably not Debian-specific,
> but I'm hoping someone on this list can help me out anyway.
>
> I upgraded to kernel 2.6.7-mm1 today.
> (source from kernel.org, built with make-kpkg)
>
> Now, my system clock
Stefano Rivoir wrote:
Felix C. Stegerman wrote:
I realise this is probably not Debian-specific,
but I'm hoping someone on this list can help me out anyway.
[...]
It's a known problem, both in early -bk and in -mm1. Either wait for
-mm2 or look for the right fix, it's been around in the lkml (an a
* Felix C. Stegerman <[EMAIL PROTECTED]>:
> I upgraded to kernel 2.6.7-mm1 today.
> (source from kernel.org, built with make-kpkg)
>
> Now, my system clock is running too fast: about 3-4x normal speed.
> This is obviously not very convenient.
Strange, my clock problems pa
Felix C. Stegerman wrote:
I realise this is probably not Debian-specific,
but I'm hoping someone on this list can help me out anyway.
[...]
It's a known problem, both in early -bk and in -mm1. Either wait for
-mm2 or look for the right fix, it's been around in the lkml (an abs
macro that failed o
I realise this is probably not Debian-specific,
but I'm hoping someone on this list can help me out anyway.
I upgraded to kernel 2.6.7-mm1 today.
(source from kernel.org, built with make-kpkg)
Now, my system clock is running too fast: about 3-4x normal speed.
This is obviously not very conve
on Mon, Sep 08, 2003 at 01:03:40AM -0700, Mark Kaufer ([EMAIL PROTECTED]) wrote:
> I was reading up on how to make my system clock set to UTC (primarily
> http://www.debian.org/doc/manuals/system-administrator/ch-sysadmin-time.html
> ) and was a bit confused by this paragraph in sec
I was reading up on how to make my system clock set to UTC (primarily
http://www.debian.org/doc/manuals/system-administrator/ch-sysadmin-time.html
) and was a bit confused by this paragraph in section 16.1:
"To change the computer to use UTC after installation, edit the file
/etc/defaul
On Mon, 25 Aug 2003 01:41 am, Rex Chan wrote:
> On Sun, Aug 24, 2003 at 01:54:49PM +1000, James
Steward<[EMAIL PROTECTED]> wrote:
> > Debian has a system configuration tool but I can't remember exactly what
> > it's called..something like base-config.
> >
> > Basically, in the file /etc/adjtime on
> On Fri, 22 Aug 2003 09:40 pm, Harry Brueckner wrote:
> > Hi there,
> >
> > I have my woody system configured to run the systems HW clock in GMT. This
> > is kinda uncomfortable because I also have a windows system running on the
> > same machine (shame on me).
> >
> > I know that I change the tim
On Sun, Aug 24, 2003 at 01:54:49PM +1000, James Steward<[EMAIL PROTECTED]> wrote:
> Debian has a system configuration tool but I can't remember exactly what it's
> called..something like base-config.
>
> Basically, in the file /etc/adjtime on the 3rd line there's either UTC or
> LOCAL.
>
> Be a
Debian has a system configuration tool but I can't remember exactly what it's
called..something like base-config.
Basically, in the file /etc/adjtime on the 3rd line there's either UTC or
LOCAL.
Be a little careful changing this by hand. When the system is shutdown the OS
checks the software
Andreas Janssen said on Fri, Aug 22, 2003 at 03:35:36PM +0200:
> Hallo
>
> Harry Brueckner (<[EMAIL PROTECTED]>) wrote:
>
> > I have my woody system configured to run the systems HW clock in GMT.
> > This is kinda uncomfortable because I also have a windows system
> > running on the same machine
Hallo
Harry Brueckner (<[EMAIL PROTECTED]>) wrote:
> I have my woody system configured to run the systems HW clock in GMT.
> This is kinda uncomfortable because I also have a windows system
> running on the same machine (shame on me).
>
> I know that I change the timezone using tzconfig but I di
Hi there,
I have my woody system configured to run the systems HW clock in GMT. This
is kinda uncomfortable because I also have a windows system running on the
same machine (shame on me).
I know that I change the timezone using tzconfig but I did not find a hint
on how to change the setting fr
On Tue, Feb 04, 2003 at 10:05:12AM +, Doug MacFarlane wrote:
> During the install, I answered one of the questions wrong - "Is your system
> clock set to GMT or Local Time". I need to dpkg-reconfigure this, but I
> have no idea what package had debconf ask me this . . .
During the install, I answered one of the questions wrong - "Is your system
clock set to GMT or Local Time". I need to dpkg-reconfigure this, but I
have no idea what package had debconf ask me this . . .
TIA
madmac
--
Doug MacFarlane
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email
also sprach Gleef <[EMAIL PROTECTED]> [2002.09.16.1846 +0200]:
> I don't know if ntpd knows how to handle SpeedStep or not. Even if it
> does, it is also possible that there is a subtle implementation bug
> causing your clock drift. Keep in mind that ntpd was really tested
> with stable servers
Ian Balchin wrote:
I can see where to accurise the clock, but cannot find where the
basic boot setting can be revised. Any suggestions?
Thanks in advance
/etc/default/rcS
-Tupshin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 10 January 2002 12:14 pm, Ian Balchin wrote:
[snip]
> I can see where to accurise the clock, but cannot find where the
> basic boot setting can be revised. Any suggestions?
Look in /etc/default/rcS. Your UTC entry is probably "yes".
Try
On Thu, Jan 10, 2002 at 08:14:06PM +0200, Ian Balchin wrote (1.00):
> I can see where to accurise the clock, but cannot find where the
> basic boot setting can be revised. Any suggestions?
Edit /etc/default/rcS and set UTC=no. Then, set your clock to the
correct time.
M
Hi,
When I did last reinstall I mistakenly selected the GMT option
because, not running windows on the same machine, i thought that it
would coexist fine with dos. Wrong!
Now the linux clock is two hours ahead of the RTC (bios) which is
obviously set at local clock-time for use when i boot dos.
Thank you guys (John and Henrique) for your prompt answers and sorry for the
words in caps - just wanted to make them stand out from the rest of my
message.
More feedback ?
---
Friedrich
PM
To: Friedrich Dumont
Cc: debian-user@lists.debian.org
Subject: Re: SETTING SYSTEM CLOCK
On Wed, 07 Mar 2001, Friedrich Dumont wrote:
> SETTING SYSTEM CLOCK USING THE HARDWARE CLOCK AS REFERENCE...
That should not be in caps, unless your terminal is seriously screwed up.
But it's a good
On Wed, 07 Mar 2001, Friedrich Dumont wrote:
> SETTING SYSTEM CLOCK USING THE HARDWARE CLOCK AS REFERENCE...
That should not be in caps, unless your terminal is seriously screwed up.
But it's a good thing to notice that patch to better document the hwclock
script paid back...
You want
r the hard disk or the boot floopy
then hangs at the following line:
SETTING SYSTEM CLOCK USING THE HARDWARE CLOCK AS REFERENCE...
- I checked the AMI BIOS setup program and even reinstalled Debian/GNU Linux
from scratch two other times choosing GMT and then local time but nothing
seems to work.
A
On Tue, Nov 28, 2000 at 09:25:27PM -0600, Brandt Dusthimer wrote:
:Sorry everyone about my system clock being messed up in some of my messages.
:My mobo battery's kind of loose so it occassionaly resets. Thanks for all
:your messages tho.
look into ntp and ntpdate, there was a recent t
Sorry everyone about my system clock being messed up in some of my messages.
My mobo battery's kind of loose so it occassionaly resets. Thanks for all
your messages tho.
Brandt Dusthimer
Quoting Guentcho Skordev ([EMAIL PROTECTED]):
>
> I have a similar but yet another problem. The battery of the clock is old,
> and the clock is wrong if the power was off.
Can you not fit a new battery? Usually you can just plug the new one
into the mobo without removing the old one. (It's usuall
> (Maybe allowing someone to type in a date, if it is possible at all, is
> somehow insecure, but I am the only user at the console).
>
try this in your ntpdate startup script:
if ! ntpdate ; then
while :; do
read -p "ntpdate failed. please enter date by hand: " date
date -s $date && br
Hello,
I have a similar but yet another problem. The battery of the clock is old,
and the clock is wrong if the power was off. It isn't a constant drift so
"hwclock --adjust" wouldn't help. Because I am connected to a network, I
have used netdate to get the correct time from the net.
But I still
Hello Owen,
On Thu, 25 May 2000, Owen G. Emry wrote:
> My firewall machine (a trusty old 486 DX4) has a bios that doesn't like the
> year 2000. It isn't a major problem but several things (e.g. make)
> complain, so is there an easy workaround?
> I assume I can just set the real-time clock to,
"Owen G. Emry" <[EMAIL PROTECTED]> writes:
> My firewall machine (a trusty old 486 DX4) has a bios that doesn't like the
> year 2000. It isn't a major problem but several things (e.g. make)
> complain, so is there an easy workaround?
>
> I assume I can just set the real-time clock to, say, 199
Sorry, already deleted the original posting:
> "Owen G. Emry" wrote:
> >
> > My firewall machine (a trusty old 486 DX4) has a bios that doesn't like the
> > year 2000. It isn't a major problem but several things (e.g. make)
> > complain, so is there an easy workaround?
> >
> > I assume I can ju
"Owen G. Emry" wrote:
>
> My firewall machine (a trusty old 486 DX4) has a bios that doesn't like the
> year 2000. It isn't a major problem but several things (e.g. make)
> complain, so is there an easy workaround?
>
> I assume I can just set the real-time clock to, say, 1990, and have the
> int
My firewall machine (a trusty old 486 DX4) has a bios that doesn't like the
year 2000. It isn't a major problem but several things (e.g. make)
complain, so is there an easy workaround?
I assume I can just set the real-time clock to, say, 1990, and have the
internal clock set itself to the RTC
On Tue, 25 Apr 2000, Harry ten Berge <[EMAIL PROTECTED]> wrote:
>Chris Mason wrote:
>> Where can I get nptdate?
>It's in 'xntp3'. ntpdate is a part of the complete 'time server suite'.
At least in potato it's broken up into server and client. There is a
ntpdate (client only) deb.
--
Philip Lehm
Chris Mason wrote:
>
> Where can I get nptdate?
>
It's in 'xntp3'. ntpdate is a part of the complete 'time server suite'.
Usually 'ntpdate' is only used to synchronize if you have big
time-differences. The ntpd can only synchronize if the difference
between the local client and the time-server i
On Fri, Apr 24, 2020 at 12:38:11PM -0400, Chris Mason wrote:
> Where can I get nptdate?
apt-get install ntpdate
--
Karsten M. Selfhttp:/www.netcom.com/~kmself
What part of "Gestalt" don't you understand?
http://gestalt-system.sourceforge.net/
GPG fingerprint: F932 8B25 5FDD 2
> Where can I get nptdate?
>
it is a normal debian package called "ntpdate" - at least in potato. ;-)
--
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Linux - the last service pack you'll ever need.
-
From: kmself@ix.netcom.com [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 23, 2000 12:59 AM
To: Debian User List
Subject: Re: how do you set your system clock from a remote time server?
On Sat, Apr 22, 2000 at 10:54:03AM -0400, Maury Merkin wrote:
> I saw, just a few days ago, a post wit
On Sat, Apr 22, 2000 at 10:54:03AM -0400, Maury Merkin wrote:
> I saw, just a few days ago, a post with a command to get the current
> time and reset the system clock.
>
> I didn't pay much attention then 'cause I thought the script I used to
> use with RH would work.
John Galt writes:
> Having said this, you might want to consider jumping protocols to the
> newer NTP and install ntpdate
Or chrony.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin
e and reset the system clock.
> >
> > I didn't pay much attention then 'cause I thought the script I used to
> > use with RH would work. They don't. (No 'rdate' and no 'clock').
>
> $ dpkg -S rdate
> netstd: /usr/man/man8/rdate.8.gz
&
th a command to get the current
> time and reset the system clock.
>
> I didn't pay much attention then 'cause I thought the script I used to
> use with RH would work. They don't. (No 'rdate' and no 'clock').
>
> Tia
>
> Maury
>
>
On Sat, Apr 22, 2000 at 08:39:19AM -0700, Pann McCuaig wrote:
> On Sat, Apr 22, 2000 at 10:54, Maury Merkin wrote:
> > I saw, just a few days ago, a post with a command to get the current
> > time and reset the system clock.
> >
> > I didn't pay much attention th
On Sat, Apr 22, 2000 at 10:54, Maury Merkin wrote:
> I saw, just a few days ago, a post with a command to get the current
> time and reset the system clock.
>
> I didn't pay much attention then 'cause I thought the script I used to
> use with RH would work. They don'
On Sat, Apr 22, 2000 at 10:54:03AM -0400,
Maury Merkin <[EMAIL PROTECTED]> wrote:
> I saw, just a few days ago, a post with a command to get the current
> time and reset the system clock.
You're looking for ntpdate.
--
Eric Gillespie, Jr. <*> [EMAIL PROTECTED]
&quo
I saw, just a few days ago, a post with a command to get the current
time and reset the system clock.
I didn't pay much attention then 'cause I thought the script I used to
use with RH would work. They don't. (No 'rdate' and no 'clock').
Tia
Maury
with the way my system clocks are setup. What I am
> trying to do is sync my local time and UTC so they are the same. At the
> moment they seem to be 10 hours apart. I have tried tzconfig but that does
> not ask if i want my system clock and hwclock to be in sync or not to refer
> to
I have a small problem with the way my system clocks are setup. What I am
trying to do is sync my local time and UTC so they are the same. At the
moment they seem to be 10 hours apart. I have tried tzconfig but that does
not ask if i want my system clock and hwclock to be in sync or not to refer
It was the problem! I disabled APM in the BIOS and let linux run overnight. The
time was accurate the following morning. I just finished rebuilding & booting
a new kernel with APM support and turned BIOS power management back on. I think
it's licked.
Thanks to all who helped me out!
Jason
>On Fr
On Fri, 24 Sep, 1999 à 09:00:25AM +, Jason Christensen wrote:
> Colin,
>
> I think that you may be right. Now that I think about it, the problem only
> seems
> to occur after linux has been running for a long period of time without a
> logon
> (i.e. overnight). I think I have the BIOS config
I had a problem with my clock drifting after I used hwclock to reset
my time after I moved to a new time zone: the box had been on 15
minutes, I set it back an hour, and when I rebooted, the /etc/adjtime
adjusted the clock by about four days. so I set it again. Now the
durn thing thought it was
Colin,
I think that you may be right. Now that I think about it, the problem only seems
to occur after linux has been running for a long period of time without a logon
(i.e. overnight). I think I have the BIOS configured to kick into sleep mode
after a certain time of inactivity. This would make s
* Laurent PICOULEAU <[EMAIL PROTECTED]> writes:
> On Thu, 23 Sep, 1999 à 10:38:18AM +, Jason Christensen wrote:
>> Would anyone be able to speculate as to why my system (kernel) clock is slow?
>> I know that my hardware (CMOS) clock is maintaining a time that does not
>> drift
>> more than a
On Thu, 23 Sep, 1999 à 10:38:18AM +, Jason Christensen wrote:
> Would anyone be able to speculate as to why my system (kernel) clock is slow?
> I know that my hardware (CMOS) clock is maintaining a time that does not
> drift
> more than a CMOS clock normally does, but my kernel clock will lo
> "J" == Jason Christensen <[EMAIL PROTECTED]> writes:
J> Would anyone be able to speculate as to why my system (kernel)
J> clock is slow? I know that my hardware (CMOS) clock is
J> maintaining a time that does not drift more than a CMOS clock
J> normally does, but my kernel clock will lose ap
Would anyone be able to speculate as to why my system (kernel) clock is slow?
I know that my hardware (CMOS) clock is maintaining a time that does not drift
more than a CMOS clock normally does, but my kernel clock will lose
approximately
4 hours in every 9.
I can set the system clock at
are you looking for NTP? that's main/net/ntp. HTH
On Mon, 5 Jul 1999, Daniel Dui wrote:
> I think there is a debian package that keeps the system time
> synchronized with GMT (well in my case with CET) .
>
> Does anyone know what is this package's name?
>
> BTW the machine is permanently con
I use cron to execute netdate (in netstd) daily to update my clock.
This is my cron script:
> #!/bin/sh
> netdate ntp.xs4all.nl uva.nl ntp.demon.nl && hwclock --systohc --utc
Try to find ntp servers near you..
Regards,
Remco
On Mon, Jul 05, 1999 at 15:42, Daniel Dui wrote:
> I think there is
Daniel Dui writes:
> I think there is a debian package that keeps the system time
> synchronized with GMT (well in my case with CET) .
> Does anyone know what is this package's name?
Look at chrony and xntp3. Chrony is only in unstable. If you install it
you will have to change the default conf
I think there is a debian package that keeps the system time
synchronized with GMT (well in my case with CET) .
Does anyone know what is this package's name?
BTW the machine is permanently connected.
thank you
daniel
--
Daniel Dui [EMAIL PRO
*- On 10 Feb, Steven Evatt wrote about "My System Clock - Under Slink"
> Howdy folks,
>
> I'm running slink (kernel version 2.0.33) on a 486 and I'm having an
> interesting problem with my uptime. I'm courious if this is a "feature"
> or a &
Let me guess.. Another person running rc5des client.. the load average gives
it away :)
> 12:00am up 75 days, 14:17, 3 users, load average: 1.02, 1.01, 1.00
> 4:00am up 75 days, 18:17, 2 users, load average: 1.00, 1.00, 1.00
> 8:00am up 75 days, 22:17, 2 users, load average: 1.00, 1.00,
Howdy folks,
I'm running slink (kernel version 2.0.33) on a 486 and I'm having an
interesting problem with my uptime. I'm courious if this is a "feature"
or a "bug".
The log below is from a cronscript that every four hours logs that my
system still has a heart beat. This is accomplished by appe
hat NTP is
supposed to allow the system clock to stay within a few milliseconds of the
time standard, this is bizarre.
Has anyone else out there had this problem, does anyone have any clues
about what's going on here, and how to fix it? Is there a FAQ or HOWTO
about this?
-Randy
1 - 100 of 101 matches
Mail list logo
