Does anyone use alarm-clock?
When an alarm is created, the sound menu is empty. Shouldn't
there be a default alarm sound at least? Is there a package
providing sounds?
Thanks,... Peter E.
--
Telephone 1 360 639 0202. Bcc: peter at easthope.ca
http://carnot.yi.org/
http
On Wed, 06 Jun 2012 08:00:55 -0800, peter wrote:
Does anyone use alarm-clock?
Mmm, never heard about it before :-)
When an alarm is created, the sound menu is empty. Shouldn't there be a
default alarm sound at least?
There's a ring.wav file under /usr/share/alarmclock folder
From: Camaleon noela...@gmail.com
Date: Wed, 6 Jun 2012 16:32:44 + (UTC)
There's a ring.wav file under /usr/share/alarmclock folder :-?
Our folders are different.
peter@dalton:~$ ls -dl /usr/share/alar*
drwxr-xr-x 2 root root 4096 Jun 1 11:20 /usr/share/alarm-clock-applet
No sounds
On Tue, 21 Feb 2012 22:31:38 -0500, Doug wrote:
On 02/21/2012 08:36 PM, Don deJuan wrote:
In windows open regedit go to:
HKLM\SYSTEM\CurrentControlSet\__Control
\TimeZoneInformation
add a DWORD with name of RealTimeIsUniversal exactly as
its
On 22/02/12 03:54, Don deJuan wrote:
Since you will not keep this in the public list I will forward your
emails to it.
Please don't, we're not interested. If someone mails you privately with
something you find disagreeable please deal with it yourself.
--
To UNSUBSCRIBE, email to
On 21/02/12 05:00, Kousik Maiti wrote:
May be the problem is with your motherboard battery... not OS ...
That only manifests itself when he boots into Windows? No, this is a
well-known problem, it's Windows.
--
Jon Dowland
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On Ma, 21 feb 12, 04:55:14, Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock as if the UCT time were actually local
time. I have no idea
On Tue, 21 Feb 2012, Andrei POPESCU wrote:
Windows initially gets the time from the hardware clock, but it may also
get the time from the internet (NTP protocol?). Since your hardware
It's SNTP nowadays, I believe. Windows has never been big on timekeeping.
Of course, the registry hack
On Mon, Feb 20, 2012 at 8:55 PM, Hendrik Boom hend...@topoi.pooq.comwrote:
I run my machine on UCT, or something like it (timezone +0). Every time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock as if the UCT time were actually local
On Tue, 21 Feb 2012, Henrique de Moraes Holschuh wrote:
On Tue, 21 Feb 2012, Andrei POPESCU wrote:
Windows initially gets the time from the hardware clock, but it may also
get the time from the internet (NTP protocol?). Since your hardware
It's SNTP nowadays, I believe. Windows has
On Tue, Feb 21, 2012 at 04:55:14AM +, Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock as if the UCT time were actually local
time. I
On Tue, 21 Feb 2012, Tony Baldwin wrote:
On Tue, Feb 21, 2012 at 04:55:14AM +, Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock
On 02/21/2012 03:42 AM, Andrei POPESCU wrote:
On Ma, 21 feb 12, 04:55:14, Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock as if the UCT time
moon) Windows
takes it on itself to set my clock as if the UCT time were actually local
time. I have no idea where it gets its idea of what the current time is.
What I'd like to know is, how can I keep Windows from messing with my
clock. I'd really like it to just leave it alone.
-- hendrik
to set my clock as if the UCT time were actually
local
time. I have no idea where it gets its idea of what the current
time is.
What I'd like to know is, how can I keep Windows from messing with my
clock. I'd really like it to just leave it alone.
Well, if you *didn't* boot into Windows once
On 2/21/2012 1:00 AM, Don deJuan wrote:
On 02/20/2012 09:51 PM, Bob Proulx wrote:
Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every
time
It's UTC. Having the hardare clock in UTC is normal and standard.
http://en.wikipedia.org/wiki
On 02/21/2012 03:58 PM, Doug wrote:
On 2/21/2012 1:00 AM, Don deJuan wrote:
On 02/20/2012 09:51 PM, Bob Proulx wrote:
Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
It's UTC. Having the hardare clock in UTC is normal and standard.
http
wrote:
On 02/20/2012 09:51 PM, Bob Proulx wrote:
Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
It's UTC. Having the hardare clock in UTC is normal and standard.
http://en.wikipedia.org/wiki/**Coordinated_Universal_Timehttp://en.wikipedia.org/wiki
It's UTC. Having the hardare clock in UTC is normal and
standard.
http://en.wikipedia.org/wiki/__Coordinated_Universal_Time
http://en.wikipedia.org/wiki/Coordinated_Universal_Time
I boot to Windows XP (which I need to do once
Sure, you can just tell people to RTFM. Or you can just post the patch.
The patch is naturally easier and takes substantially less effort to
create and post than being a dick about it on an internationally
distributed mailing list.
On Tue, Feb 21, 2012 at 5:36 PM, Don deJuan
On 02/21/2012 08:36 PM, Don deJuan wrote:
In windows open regedit go to:
HKLM\SYSTEM\CurrentControlSet\__Control\TimeZoneInformation
add a DWORD with name of RealTimeIsUniversal exactly as
its entered
there and set the value to 1. Now
Or behave like you and calling me childish names, or you still in high
school? Fricken read what I posted 3 times oh brilliant one. And IF YOU
wish to contribute a patch to MS for that or to the list then PLEASE do
so. I CHOOSE NOT TO. I spoon fed you 3 times grow up and read, follow
posted
On 02/21/2012 07:31 PM, Doug wrote:
On 02/21/2012 08:36 PM, Don deJuan wrote:
In windows open regedit go to:
HKLM\SYSTEM\CurrentControlSet\__Control\TimeZoneInformation
add a DWORD with name of RealTimeIsUniversal exactly as
its entered
there and set the value to 1. Now you can have windows
the time to actually read everything I
stated in my responses.
Original Message
Subject:Re: Windows screws up Linux's clock
Date: Tue, 21 Feb 2012 19:45:12 -0800
From: Paul Johnson ba...@ursamundi.org
To: Don deJuan donjuans...@gmail.com
Don't let the door
On 02/21/2012 06:24 PM, Paul Johnson wrote:
Sure, you can just tell people to RTFM. Or you can just post the patch.
The patch is naturally easier and takes substantially less effort to
create and post than being a dick about it on an internationally
distributed mailing list.
On Tue, Feb 21,
On Tue, Feb 21, 2012 at 10:03 PM, Don deJuan donjuans...@gmail.com wrote:
I only continue this banter because I find your assumptions and responses to
be hilarious, already been forwarded around work. Please keep your witty,
brilliant responses coming as to why I was such the dick with this
I run my machine on UCT, or something like it (timezone +0). Every time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock as if the UCT time were actually local
time. I have no idea where it gets its idea of what the current time
it on itself to set my clock as if the UCT time were actually local
time. I have no idea where it gets its idea of what the current time is.
What I'd like to know is, how can I keep Windows from messing with my
clock. I'd really like it to just leave it alone.
-- hendrik
--
To UNSUBSCRIBE
Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
It's UTC. Having the hardare clock in UTC is normal and standard.
http://en.wikipedia.org/wiki/Coordinated_Universal_Time
I boot to Windows XP (which I need to do once in a blue moon) Windows
On 02/20/2012 09:51 PM, Bob Proulx wrote:
Hendrik Boom wrote:
I run my machine on UCT, or something like it (timezone +0). Every time
It's UTC. Having the hardare clock in UTC is normal and standard.
http://en.wikipedia.org/wiki/Coordinated_Universal_Time
I boot to Windows XP (which
Hendrik Boom hend...@topoi.pooq.com writes:
I run my machine on UCT, or something like it (timezone +0). Every time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock as if the UCT time were actually local
time. I have no idea where
On 02/20/2012 09:55 PM, Joe Pfeiffer wrote:
Hendrik Boomhend...@topoi.pooq.com writes:
I run my machine on UCT, or something like it (timezone +0). Every time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock as if the UCT time were
On 02/20/2012 09:55 PM, Joe Pfeiffer wrote:
Hendrik Boomhend...@topoi.pooq.com writes:
I run my machine on UCT, or something like it (timezone +0). Every time
I boot to Windows XP (which I need to do once in a blue moon) Windows
takes it on itself to set my clock as if the UCT time were
Bob Proulx b...@proulx.com wrote:
I would look for a file on the
filesystem that is always active on the system. I would extract the
time from that file and use it as the basis for the new system time.
Then at the very least you would have monotonically increasing time.
That's a really good
On Tue, 27 Sep 2011 10:11:33 +0100, David wrote in message
201109271011.33513.david.goodeno...@btconnect.com:
Does anyone know if there is a way to tell and of the crons to
ignore unset times?
..keep your script _simple_, on shutdowns or reboots etc
(and unless you have very short life
that cron (and I am quite happy to looks at
other crons if that makes like easy) does not use an unset clock as the
basis for firing commands.
There are also /etc/cron.hourly|daily|weekly folders where you can put
your scripts which will be run by cron at no specific time, not sure if
this can
the
hardware clock is always Thu, 01 Jan 1970 00:00:00 +, right?
Yes
I then set the time using NTP once I have a network connection -
wireless as it happens and therefore not entirely predictable in how
quickly it will connect.
Here are some suggestions. I haven't encountered this problem
can consier in adding an RTC (if not present in motherboard) or
an external battery to get a clock at booting, if not atomically synced,
at least with decent values.
Having a system configured with bad time may experience stability
issues as most of the base scripts rely on the right time to run
David Goodenough wrote:
Bob Proulx wrote:
Then I would create a new script that would set the clock to as
reasonable of a value as possible. You don't have a real time value
yet but most importantly you don't want to set it to a time that is
before the system was stopped. So I would
it will connect.
I would like to make sure that cron (and I am quite happy to
looks at other crons if that makes like easy) does not use an
unset clock as the basis for firing commands.
I could use update-rc.d to disable cron, and only enable it
once wpa_supplicant has established the connection
Le 15244ième jour après Epoch,
David Goodenough écrivait:
[...]
I could use update-rc.d to disable cron, and only enable it
once wpa_supplicant has established the connection, but then
what if the wireless link goes down and back up while the
hardware is powered up, in which case it would
David Goodenough david.goodeno...@btconnect.com wrote:
I could use update-rc.d to disable cron, and only enable it
once wpa_supplicant has established the connection, but then
what if the wireless link goes down and back up while the
hardware is powered up, in which case it would get
that cron (and I am quite happy to looks at
other crons if that makes like easy) does not use an unset clock as the
basis for firing commands.
There are also /etc/cron.hourly|daily|weekly folders where you can put
your scripts which will be run by cron at no specific time, not sure if
this can
David Goodenough wrote:
I have some small single board systems on which I run Debian.
They have clocks, but they are not battery backed and so reset
to zero for each run.
And by reset to zero you mean the date loaded at boot time from the
hardware clock is always Thu, 01 Jan 1970 00:00:00
current/real date and system date is too wide.
That used to be true with older versions of Debian when there was a
separate 'ntpdate' package. 'ntpdate' would be run to step the clock
before starting the 'ntp' daemon. If you only ran 'ntp' then if the
time were too far off (1000s) then ntpd would
Hello, the server clock continually recedes as you can see the ntpq -p
offset is too high.
Setting the right time at hand not solve anything after a while the
server clock slowly recedes
Any suggestions?
remote refid st t when poll reach delay offset jitter
Hell List:
On 09/08/11 09:40, owl...@gmail.com wrote:
Hello, the server clock continually recedes as you can see the ntpq -p
offset is too high.
Setting the right time at hand not solve anything after a while the
server clock slowly recedes
Any suggestions?
ahve you tried an other server
2011/8/9 Jerome BENOIT g62993...@rezozer.net:
Hell List:
On 09/08/11 09:40, owl...@gmail.com wrote:
Hello, the server clock continually recedes as you can see the ntpq -p
offset is too high.
Setting the right time at hand not solve anything after a while the
server clock slowly recedes
On 8/9/2011 2:40 AM, owl...@gmail.com wrote:
remote refid st t when poll reach delay offset jitter
==
ntp1.inrim.it .CTD.1 u 46 64 377 23.641 329686. 2517.77
.
In that case your system board will probably need to be replaced.
In many cases, judicious use of adjtimex to trim the system clock
can avoid a system board replacement.
Rick
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
On 8/9/2011 6:55 AM, Rick Thomas wrote:
In many cases, judicious use of adjtimex to trim the system clock can
avoid a system board replacement.
And if the machine is under depot warranty? Better yet, that + on-site
service contract? If it does turn out to be defective hardware
to that.
Berfore inserting nomodify the clock lost 2 minutes in 1 hour, now is
stable, i can't hunderstand how can localhost modify ntpd but this was
the only explanation, can you help me hunderstand?
remote refid st t when poll reach delay offset jitter
installation.
It was up for 181 days prior to that.
Berfore inserting nomodify the clock lost 2 minutes in 1 hour, now is
stable,
That's the rate of change you see right now, but it may or may not
remain constant. I'd give it a few days before stamping it as stable
or problem solved.
i can't
[7.129981] CPU0: Temperature above threshold, cpu clock throttled (total
events = 74)
[7.130633] CPU0: Temperature/speed normal
[7.141110] CPU0: Temperature above threshold, cpu clock throttled (total
events = 75)
[7.141763] CPU0: Temperature/speed normal
[7.151465] CPU0
On Thu, Jul 14, 2011 at 07:15:49PM +0530, surreal wrote:
[7.129981] CPU0: Temperature above threshold, cpu clock throttled (total
events = 74)
[7.130633] CPU0: Temperature/speed normal
[7.141110] CPU0: Temperature above threshold, cpu clock throttled (total
events = 75
looking for an count-down clock. Features are:
(...)
If you find no aplication that suits your needs, may I suggest a do-
it-yourself work? :-)
Dialog (command line ncurses scripting) and xdialog (GUI) can help you
here. It's very easy to use and just basic bash programming skills
needed
T o n g wrote:
The following shell script will work:
--
#!/bin/sh
sleep $1
beep
-
name it 'alarm' and 'alarm 30' will alarm you after 30 seconds.
That works if you know how many seconds to wait. Let's say that it is
Mon, 17 Jan 2011
On Tue, 04 Jan 2011 13:11:24 +, Camaleón wrote:
Hello. I am looking for an count-down clock. Features are:
(...)
If you find no aplication that suits your needs, may I suggest a do-
it-yourself work? :-)
Dialog (command line ncurses scripting) and xdialog (GUI) can help you
here
Hello. I am looking for an count-down clock. Features are:
* count down to up to 300 seconds. I wish to configure my fluxbox to
activate it by Ctrl+6, which counts down 60 seconds, Ctrl+3 to
count down 30 seconds, thus it must be able to accept commandline
parameter
On Tue, 04 Jan 2011 20:06:30 +0800, Zhang Weiwu wrote:
Hello. I am looking for an count-down clock. Features are:
(...)
If you find no aplication that suits your needs, may I suggest a do-
it-yourself work? :-)
Dialog (command line ncurses scripting) and xdialog (GUI) can help you
here. It's
Camaleón wrote:
On Tue, 04 Jan 2011 20:06:30 +0800, Zhang Weiwu wrote:
Hello. I am looking for an count-down clock. Features are:
(...)
If you find no aplication that suits your needs, may I suggest a do-
it-yourself work? :-)
Dialog (command line ncurses scripting) and xdialog (GUI) can
pe After chronyc settime 16:50 the clock displays 4:50.
From: John Hasler jhas...@debian.org
Date: Mon, 27 Dec 2010 19:39:19 -0600
What did it display before the chronyc command?
4:50 ... or might have been 4:49. I click slowly.
My explanation should have been more clear. In the BIOS
Folk,
Clock Format is set to %R, which according to strftime.man
specifies a 24 hour format.
After chronyc settime 16:50 the clock displays 4:50.
Am I misusing chronyc? Is the digital clock in LXDE unable
to display the 24 hour format?
Thanks for any ideas, ... Peter E
On Mon, 27 Dec 2010 05:01:19 -0700
peasth...@shaw.ca wrote:
Folk,
Clock Format is set to %R, which according to strftime.man
specifies a 24 hour format.
After chronyc settime 16:50 the clock displays 4:50.
Am I misusing chronyc? Is the digital clock in LXDE unable
to display
peasthope writes:
Clock Format is set to %R, which according to strftime.man specifies
a 24 hour format.
Try %H:%M:%S
After chronyc settime 16:50 the clock displays 4:50.
What did it display before the chronyc command?
Am I misusing chronyc?
Chronyc merely talks to chronyd which messes
Slicky Johnson writes:
Perhaps when evoking 'settime' chrony adds it's own format.
Chrony does nothing that has anything to do with formats.
--
John Hasler
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
El Fri, 15 Jan 2010 21:19:29 -0500, David Rios escribió:
On Sat, 2010-01-16 at 00:14 -0200, Javier Marta wrote:
Si no me equivoco, es posible indicarle un lugar mediante latitud y
longitud. Averiguá las coordenadas de tu ciudad y probá. Un saludo.
Gracias Javier, sí es posible y lo ubica
On Sat, 2010-01-16 at 10:59 +, Camaleón wrote:
El Fri, 15 Jan 2010 21:19:29 -0500, David Rios escribió:
On Sat, 2010-01-16 at 00:14 -0200, Javier Marta wrote:
Si no me equivoco, es posible indicarle un lugar mediante latitud y
longitud. Averiguá las coordenadas de tu ciudad y probá.
Hola a todos.
He buscado mucho en Google y no doy con la respuesta a mi duda, asi
que recurro a ustedes.
Al abrir el applet Clock que por defecto se encuentra en la parte
derecha del panel superior de Gnome, da la posibilidad de agregar
lugares (locations en ingles) para mostrar el estado del
El sáb, 16-01-2010 a las 00:14 -0200, Javier Marta escribió:
El Fri, 15 Jan 2010 20:56:32 -0500
David Rios dri...@une.net.co escribió:
Hola a todos.
He buscado mucho en Google y no doy con la respuesta a mi duda, asi
que recurro a ustedes.
Al abrir el applet Clock que por defecto
El Fri, 15 Jan 2010 20:56:32 -0500
David Rios dri...@une.net.co escribió:
Hola a todos.
He buscado mucho en Google y no doy con la respuesta a mi duda, asi
que recurro a ustedes.
Al abrir el applet Clock que por defecto se encuentra en la parte
derecha del panel superior de Gnome, da la
On Sat, 2010-01-16 at 00:14 -0200, Javier Marta wrote:
El Fri, 15 Jan 2010 20:56:32 -0500
David Rios dri...@une.net.co escribió:
Hola a todos.
He buscado mucho en Google y no doy con la respuesta a mi duda, asi
que recurro a ustedes.
Al abrir el applet Clock que por defecto se
recurro a ustedes.
Al abrir el applet Clock que por defecto se encuentra en la parte
derecha del panel superior de Gnome, da la posibilidad de agregar
lugares (locations en ingles) para mostrar el estado del tiempo; sin
embargo mi ciudad no esta en la lista. Como puedo agregarlo
upgraded the kernel to
linux-image-2.6.26-2-686_2.6.26-19 in the 3 boxes running Lenny. Now
those boxes are repeatedly freezing because the system clock seems to
stall. Forcing the kernel to use acpi_pm as clocksource instead of TSC
and disabling TSC doesn't seems to help. So, does anybody
-686_2.6.26-19 in the 3 boxes running Lenny. Now
those boxes are repeatedly freezing because the system clock seems to
stall. Forcing the kernel to use acpi_pm as clocksource instead of TSC
and disabling TSC doesn't seems to help. So, does anybody have any
suggestion on how to fix this?
I've
boxes are repeatedly freezing because the system clock seems to
stall. Forcing the kernel to use acpi_pm as clocksource instead of TSC
and disabling TSC doesn't seems to help. So, does anybody have any
suggestion on how to fix this?
Thanks
Eric L.
--
To UNSUBSCRIBE, email to debian-user
Lenny. Now
those boxes are repeatedly freezing because the system clock seems to
stall. Forcing the kernel to use acpi_pm as clocksource instead of TSC
and disabling TSC doesn't seems to help. So, does anybody have any
suggestion on how to fix this?
Thanks
Eric L.
boot back
I have an embedded board (a PCEngines Wrap board) which has no
persistent clock. With earlier configurations I set the clock with ntpdate
once the network was up.
But with current sid I have a problem in that fsck in util-linux-ng 2.16
complains that the Superblock last mount time (Sat Jan 1
On Wed, Aug 26, 2009 at 01:57:20PM +0100, David Goodenough wrote:
I have an embedded board (a PCEngines Wrap board) which has no
persistent clock. With earlier configurations I set the clock with ntpdate
once the network was up.
interesting. I have no experience with this sort of installation
On Wednesday 26 August 2009, Andrew Sackville-West wrote:
On Wed, Aug 26, 2009 at 01:57:20PM +0100, David Goodenough wrote:
I have an embedded board (a PCEngines Wrap board) which has no
persistent clock. With earlier configurations I set the clock with
ntpdate once the network was up
Olá!
Já faz algum tempo que tenho observado que o gnome do debian, o
applet-clock não tem a opção weather, ou seja, não abre aquela opção
abaixo do calendário quando se clica no relógio do painel.
Eu pensei que fosse uma opção dos empacotadores do debian. Mas
observei que a versão testing tem
On 01 Jun 2009, Vincent Lefevre wrote:
On 2009-06-01 09:40:44 +, Tzafrir Cohen wrote:
On Mon, Jun 01, 2009 at 11:16:01AM +0200, Vincent Lefevre wrote:
On 2009-06-01 11:08:37 +0200, K. Jantzen wrote:
Where can I set the internal clock?
With the date or ntpdate (better) command
Where can I set the internal clock?
--
K. Jantzen
Debian Lenny 5.0 amd64
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
2009/6/1 K. Jantzen k.d.jant...@t-online.de:
Where can I set the internal clock?
hwclock --systohc
If the hardware clock is drifting it might be better to install
openntpd It will gradually pull your system clock into calibration and
keep it there.
Adrian
--
24x7x365 != 24x7x52 Stupid or bad
On 2009-06-01 11:08:37 +0200, K. Jantzen wrote:
Where can I set the internal clock?
With the date or ntpdate (better) command.
--
Vincent Lefèvre vinc...@vinc17.org - Web: http://www.vinc17.org/
100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/
Work: CR INRIA - computer
On Mon, Jun 01, 2009 at 11:16:01AM +0200, Vincent Lefevre wrote:
On 2009-06-01 11:08:37 +0200, K. Jantzen wrote:
Where can I set the internal clock?
With the date or ntpdate (better) command.
Those set the system (software) clock and not the hardware clock on the
board, though.
--
Tzafrir
On 2009-06-01 09:40:44 +, Tzafrir Cohen wrote:
On Mon, Jun 01, 2009 at 11:16:01AM +0200, Vincent Lefevre wrote:
On 2009-06-01 11:08:37 +0200, K. Jantzen wrote:
Where can I set the internal clock?
With the date or ntpdate (better) command.
Those set the system (software) clock
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 motherboards
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
. Four minutes per hour is
66,667 parts per million. You can do better than that with an rc
oscillator.
ponga wrote:
Ithink the hwclock is not much better as far as accuracy goes, but have
not analyzed it as close as the system clock.
Check the hardware (BIOS) clock. I think you'll find
the hwclock is not much better as far as accuracy goes, but have
not analyzed it as close as the system clock.
Check the hardware (BIOS) clock. I think you'll find that it is keeping
reasonable time. If it isn't return the board.
--
John Hasler
--
To UNSUBSCRIBE, email to debian-user-requ
.
Just for my information: why is chrony better than eg. ntp? I thought
the ntp daemon also adjusted the clock rate to synchronise the system
with the online ntp-servers. Am I wrong?
Sjoerd
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary
Sjoerd writes:
Just for my information: why is chrony better than eg. ntp? I thought the
ntp daemon also adjusted the clock rate to synchronise the system with
the online ntp-servers.
Chrony corrects the clock more quickly when it is far off, does a better
job of keeping it correct when you
John Hasler wrote:
Sjoerd writes:
Just for my information: why is chrony better than eg. ntp? I thought the
ntp daemon also adjusted the clock rate to synchronise the system with
the online ntp-servers.
Chrony corrects the clock more quickly when it is far off, does a better
job of keeping
John Hasler wrote:
Sjoerd writes:
Just for my information: why is chrony better than eg. ntp? I thought the
ntp daemon also adjusted the clock rate to synchronise the system with
the online ntp-servers.
Chrony corrects the clock more quickly when it is far off, does a better
job of keeping
Hugo writes:
I'm using chrony for years. But this last change to DST I had to do a
makestep in chronyc for the change to take effect.
Chrony neither cares nor knows about DST, nor does the kernel. That's
handled by the time zone stuff. Do you have your hardware (BIOS) clock on
local time
: 27655.2916667
ppm
...
The clock source is currently HPET, I've heard of people disabling
ACPI to fix the drift, or specifying a different clock source.. but
I'm not sure which is the solution...
Anyway, thanks guys. I'll try chrony, and perhaps some other tricks...
--ponga
--
To UNSUBSCRIBE, email
) clock on
local time?
Yes.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
that with an rc
oscillator.
ponga wrote:
Ithink the hwclock is not much better as far as accuracy goes, but have
not analyzed it as close as the system clock.
Check the hardware (BIOS) clock. I think you'll find that it is keeping
reasonable time. If it isn't return the board.
--
John
Greetings Debian Masters!
I've just assembled two linux systems, both with identical (brand new)
Gigabyte mobo's, though my Debian Lenny is running a slightly slower
AMD dual core proc than the other Ubuntu Intrepid system.
My problem is some SERIOUS system clock drift on the Lenny system
101 - 200 of 989 matches
Mail list logo
