On Mon, Sep 8, 2008 at 8:25 PM, 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.
>
> Recent kernels know how to read a RTC in UTC and set the initial system time
>
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
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 linked in rcS.d/ hwclock.sh and hwclockfirst.sh. Can
I di
On Sun, 07 Sep 2008, 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 sure you
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 could be going wrong
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? (Inte
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
> -74779.179229 sec
>
> if i'm co
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.
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 middle age cr
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 is running too fast: about
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 passed away with kernel 2.
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
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
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
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
Edit /etc/default/rcS
In the line that says GMT make sure its GMT="" and not GMT"-u"
After fixing that run /etc/init.d/hwclock.sh start
I had the same problem.
~Sam
On Sat, 8 Apr 2000, Doug Bean << Mr Bean's Internet >> wrote:
> I have a small problem with the way my system clocks are setup.
40 matches
Mail list logo
