Re: setting hardware clock from NIST

From: David Z Maze [EMAIL PROTECTED] If you install ntp-simple it will start a daemon that will periodically poll the time servers and gently keep your clock in sync. (If you're five seconds off, that time will be made up gradually, rather than abruptly shifting the clock.) No need to set

Re: UUCP Usenet (was Re: NTP packages (was: setting hardware clock from NIST))

Ron Johnson wrote: Bob Proulx wrote: In the beginning systems were isolated. There was no net. Then UUCP brought light unto the darkness. This was called USENET and we saw I thought that Unix-Unix cp was for, well, copying files, of which Usenet files were only a subset? UUCP

Re: setting hardware clock from NIST

[EMAIL PROTECTED] (Haines Brown) writes: I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w It's almost certainly better to find a local time server and not hammer on the NIST's; I'd also use ntp (ntp-simple package) to keep your clock up

Re: setting hardware clock from NIST

ScruLoose wrote: On Tue, Nov 04, 2003 at 09:04:58PM -0500, Haines Brown wrote: uhm... apropos clock on my box returns clock (3)- Determine processor time clock (8)- query and set the hardware clock (RTC) hwclock (8) - query and set the hardware clock (RTC

Re: setting hardware clock from NIST

From: David Z Maze [EMAIL PROTECTED] [EMAIL PROTECTED] (Haines Brown) writes: I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w It's almost certainly better to find a local time server and not hammer on the NIST's; I'd also

Re: setting hardware clock from NIST

hwclock Haines Brown wrote: I'm a RedHat refugee, and sometimes I can just transfer things to debian, and sometimes not. I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w I installed rdate, and that seems to work fine to set the system clock

Re: setting hardware clock from NIST

stratum-1 servers and stratum-2 servers on the other side of the Big Pond, look at http://www.eecis.udel.edu/~mills/ntp/clock2a.html to find some servers closer to home. The backbone will be happier and your clock will be more accurate. -- Kirk Strauser In Googlis non est, ergo non est. pgp0.pgp

Re: setting hardware clock from NIST

The first place to look for time servers is your ISP. ISPs often run time service on their nameservers. Try them. -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

Re: setting hardware clock from NIST

on the precious stratum-1 servers and stratum-2 servers on the other side of the Big Pond, look at http://www.eecis.udel.edu/~mills/ntp/clock2a.html to find some servers closer to home. The backbone will be happier and your clock will be more accurate. I already consulted that list. My home

Re: setting hardware clock from NIST

John Hasler wrote: The first place to look for time servers is your ISP. ISPs often run time service on their nameservers. Try them. I tried my ISP first. When I sent tech support an email asking about the NTP servers, they sent me instructions on how to setup news access. I had to explicitly

Re: setting hardware clock from NIST

At 2003-11-06T02:18:09Z, Roberto Sanchez [EMAIL PROTECTED] writes: I already consulted that list. My home is in Orlando, FL :-) I only got an @yahoo.es account... Gotcha. I saw the .es and, well, you can guess. But you still shouldn't use ntp2.usno.navy.mil; every little shareware time

Re: setting hardware clock from NIST

Don't _ask_ your ISP about timeservers: their first line support is just about guaranteed to be clueless. Just stick the nameserver IP numbers in the Chrony or Ntp config file and try them. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email

Re: setting hardware clock from NIST

On Wed, 2003-11-05 at 20:20, Roberto Sanchez wrote: John Hasler wrote: The first place to look for time servers is your ISP. ISPs often run time service on their nameservers. Try them. I tried my ISP first. When I sent tech support an email asking about the NTP servers, they sent me

Re: setting hardware clock from NIST

Ron Johnson wrote: On Wed, 2003-11-05 at 20:20, Roberto Sanchez wrote: John Hasler wrote: The first place to look for time servers is your ISP. ISPs often run time service on their nameservers. Try them. I tried my ISP first. When I sent tech support an email asking about the NTP servers,

NTP packages (was: setting hardware clock from NIST)

Can someone summarize the different ntp packages? For example what to run on a server vs. on an internal NAT'ed workstation. Or what is best for a dialup ADSL connection vs. full-time connection. Do all packages provied a daemon? I'm using both chrony and ntp on various machines, and it

setting hardware clock from NIST

I'm a RedHat refugee, and sometimes I can just transfer things to debian, and sometimes not. I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w I installed rdate, and that seems to work fine to set the system clock (or at least the system

Re: setting hardware clock from NIST

Haines Brown wrote: I'm a RedHat refugee, and sometimes I can just transfer things to debian, and sometimes not. I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w I installed rdate, and that seems to work fine to set the system clock

Re: setting hardware clock from NIST

On Tue, Nov 04, 2003 at 09:04:58PM -0500, Haines Brown wrote: I'm a RedHat refugee, and sometimes I can just transfer things to debian, and sometimes not. I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w I installed rdate

Re: setting hardware clock from NIST

On Tue, Nov 04, 2003 at 09:04:58PM -0500, Haines Brown wrote: So my first question is, what is debian's equivalent to clock. All it did, with the -w option, was to set the hardware clock from the system clock. I presume the former is GMT, and so there is a time offset invoved. hwclock -w

how do get my printer and clock icon back on tool bar

Setting system clock to UTC -- how?

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/default/rcS

Re: Setting system clock to UTC -- how?

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 section 16.1

Re: System clock GMT or not

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 kernel clock and compares to the hardware clock. The error is written to this file so that next time you power up, the kernel automatically adjusts

Re: System clock GMT or not

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 timezone using

Re: System clock GMT or not

kernel clock and compares to the hardware clock. The error is written to this file so that next time you power up, the kernel automatically adjusts for drift in the hardware clock. If you go and change it from UTC to LOCAL the kernel will think there is a big error (up to 24 hours I guess

Re: System clock GMT or not

careful changing this by hand. When the system is shutdown the OS checks the software kernel clock and compares to the hardware clock. The error is written to this file so that next time you power up, the kernel automatically adjusts for drift in the hardware clock. If you go and change

System clock GMT or not

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

Re: System clock GMT or not

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 did

Re: System clock GMT or not

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 (shame

Al arrancar se para en: Setting the System Clock using the Hardware Clock as reference...

Hola a todos! Utilizo el kernel 2.4.20 con el patch para placas base nforce2 hasta ahora funcionaba todo bien. Pero desde hace dos dias se me queda el PC en el arranque parado, en : System time was Tue Aug 5 06:43:17 UTC 2003 Setting the System Clock using the Hardware Clock as reference

bad hardware clock correction

as possible. I've looked at various ntp packages in Debian and it seems that they all want to set the hardware clock as well as the software clock... Does anyone know a way of getting one of the ntp packages to set the software clock without setting the hardware clock? Is there any way to compensate

gnome-panel-data: clock applet disappears when told to show the date

it? Kind regards, Jakob Sandholm -Forwarded Message- From: Jakob Sandholm [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Cc: Jakob Sandholm [EMAIL PROTECTED] Subject: gnome-panel-data: clock applet disappears when told to show the date Date: 28 Jun 2003 14:32:53 +0200

Re: dvd slow and slows clock

Thanks, I know what DMA means. I just never heard that disabling DMA for a device will cause the system clock to run at 1/3 speed. I've run other disks with DMA disabled. But maybe thats really it. As for the USB 2 linked device, I am not sure... I know that DMA is disabled on CD/DVD

Re: dvd slow and slows clock

wonder why not using dma would slow the clock down, etc... DMA is Direct Memory Access... If it is not enabled the CPU uses cycles to transfer data from the device to the memory; with DMA enabled the device transfers data directly to the memory, bypassing the CPU... that is why if you do not have

dvd slow and slows clock

/s and the desktop has bad very response time during this time and the system clock runs very slow. The mouse in particular will hang for a second or so at a time. Its something like a 12x dvd, Athlon 1800+ with 1GB Mushkin RAM. I don't get it. I have tried shuffling pci cards, switch things around

Re: dvd slow and slows clock

the files to hard drive. But the transfer is slow, about 1MB/s and the desktop has bad very response time during this time and the system clock runs very slow. The mouse in particular will hang for a second or so at a time. You probably don't have DMA activated. I have my DVD on /dev/hdc, and I

Set hw clock to local time instead of UTC?

Silly question 2 of 3: Now that my dual boot is working again, I'd like the time to be correct when I run Windows. I know that during installation I can tell the system that the hw clock should be local time, but can't seem to find out to switch it now. Doesn't seem to be covered in the docs

Re: Set hw clock to local time instead of UTC?

On Fri, 30 May 2003 10:08:40 -0700 [EMAIL PROTECTED] wrote: Silly question 2 of 3: Now that my dual boot is working again, I'd like the time to be correct when I run Windows. I know that during installation I can tell the system that the hw clock should be local time, but can't seem to find

Re: Set hw clock to local time instead of UTC?

* [EMAIL PROTECTED] ([EMAIL PROTECTED]) [030530 10:28]: Silly question 2 of 3: Now that my dual boot is working again, I'd like the time to be correct when I run Windows. I know that during installation I can tell the system that the hw clock should be local time, but can't seem to find out

Re: Set hw clock to local time instead of UTC?

Vineet Kumar declaimed: * [EMAIL PROTECTED] ([EMAIL PROTECTED]) [030530 10:28]: Silly question 2 of 3: Now that my dual boot is working again, I'd like the time to be correct when I run Windows. I know that during installation I can tell the system that the hw clock should be local time

Re: Set hw clock to local time instead of UTC?

Paul Mackinney writes: Why doesn't 'apropos UTC' find this? The option is documented in the rcS man page. Apropos searches only the short description that follows the name. -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED]

Bei Neuinstallation haengengeblieben (setting the system clock...)

Hallo Liste, Bei der Neuinstallation (Erstinstallation) von Debian Woody 3.0 (mit BF24 gestartet und dann per http installiert) bleibt mein Rechner an folgender Stelle haengen : setting the system clock using the hardware clock as reference ... der Cursor blinkt. Mit ctrl-C geht es weiter, er

very slow Linux clock

Hi All, I have big trouble with my Linux Clock: it is very slow, so [1] the time becomes quickly wrong and [2] updates with NTP stuff (or others) seems ridiculous. How can we fix it ? Thank in advance, Jerome -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe

Re: very slow Linux clock

On Son, 16 Feb 2003 at 15:05 (+0200), Jerome BENOIT wrote: I have big trouble with my Linux Clock: it is very slow, so [1] the time becomes quickly wrong and [2] updates with NTP stuff (or others) seems ridiculous. How can we fix it ? I'm not sure, but try to delete /etc/adjtime, set up

Re: very slow Linux clock

On Sun, Feb 16, 2003 at 04:50:39PM +0100, Jan Trippler wrote: On Son, 16 Feb 2003 at 15:05 (+0200), Jerome BENOIT wrote: I have big trouble with my Linux Clock: it is very slow, so [1] the time becomes quickly wrong and [2] updates with NTP stuff (or others) seems ridiculous. How can

APM and Linux Clock (WAS:Re: very slow Linux clock)

Thanks for your reply: since I have remove the `Batterie Charge Monitor' applet (Gnome2 under testing/unstable) the Linux clock is fine. Is there a link between this aapplet (APM) and the Linux clock ? Thanks, Jerome Jan Trippler wrote: On Son, 16 Feb 2003 at 15:05 (+0200), Jerome BENOIT

Re: APM and Linux Clock (WAS:Re: very slow Linux clock)

On Sun, Feb 16, 2003 at 07:18:00PM +0200, Jerome BENOIT wrote: Thanks for your reply: since I have remove the `Batterie Charge Monitor' applet (Gnome2 under testing/unstable) the Linux clock is fine. Is there a link between this applet (APM) and the Linux clock ? The APM driver disables

Default Treatment of the System Clock

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 to [EMAIL

Re: Default Treatment of the System Clock

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 . . . That's base-config, and I

Re: Clock jumping....

): icmp_seq=5 ttl=236 time=0.000 ms Googled: ,,The reason it says time of day goest back, is your system clock is not synced to the rest of the network. Try the command ntpdate. I had to download the new version for it to recognize any time servers. (try doing a search on google

Re: ntpd; local clock reference 127.127.1.0

to outside machines when the link is up, and to just provide time to the inside machines when the link is down. Another question: If I do get this to work, will the ntpd on seal continue to correct the time even when the outside link is down and the local clock is being used as reference? Have

Re: ntpd; local clock reference 127.127.1.0

[ quotes are not in chronological order ] * Brenda J. Butler [EMAIL PROTECTED] [2002-12-31 18:43:19 -0500]: Another question: If I do get this to work, will the ntpd on seal continue to correct the time even when the outside link is down and the local clock is being used as reference? Yes

Re: ntpd; local clock reference 127.127.1.0

On 2002.12.31 17:51 Brenda J. Butler wrote: I get the following in my logs [manually wrapped for legibility in email] Dec 31 15:44:27 seal ntpd[17700]: attempt to configure \ invalid address 127.127.1.0 when I set the following in /etc/ntp.conf: server 127.127.1.0

ntpd; local clock reference 127.127.1.0

when the link is down. If I don't define a reference clock (127.127.1.0), then eventually seal loses synchronisation with the outside clocks and slips to stratum 16. Then the inside ntpds refuse to sync with seal and all the machines go off on their own. I'd rather they all stick together

Re: ntpd; local clock reference 127.127.1.0

On Tue, Dec 31, 2002 at 05:51:45PM -0500, Brenda J. Butler wrote: when I set the following in /etc/ntp.conf: server 127.127.1.0 fudge 127.127.1.0 stratum 10 Why? 127.0.0.0/8 is localhost. -- .''`. Baloo [EMAIL PROTECTED] : :' :proud Debian admin and user `. `'` `-

Re: ntpd; local clock reference 127.127.1.0

machines when the link is down. Another question: If I do get this to work, will the ntpd on seal continue to correct the time even when the outside link is down and the local clock is being used as reference? -- bjb at achilles dot net Welcome to the GNU age! http://www.gnu.org 5F82 9855 E247

Re: Speaking of ntp, yes CD-R does mess with the clock!

Rob Weir [EMAIL PROTECTED] [2002-12-25 04:20:20 +1100]: Chrony is designed to work with intermittent connections. ntpd works well with intermittent connections too. No idea...chrony is a lot smarter than ntpdate though; it gradually moves your clock back and forth so that running apps don't

Re: chrony (was: Speaking of ntp, yes CD-R does mess with the clock!)

Bill Moseley writes: I don't really understand how chrony maintains the hardware clock. I know chrony can deal with a slow or fast rtc, but it seems like a good idea to update the rtc to the real time every once in a while. I agree. File a wishlist bug so I don't forget and I'll send

RE: Re: clock skew detected

recompilar el kernel modificando parámetros de la placa, eso hice, aunque de la placa no me deja modificar nada, cambié el procesador y al hacer el make dep me sale en casi todas las lineas que compila el warning clock skew detected , para quien no sepa cual era el error que me aparece era este

Re: Speaking of ntp, yes CD-R does mess with the clock!

On Tue, Dec 24, 2002 at 06:36:22AM -0800, Bill Moseley wrote: Any idea why it conflicts with ntpdate? Installing it remvoed ntpdate. ntp didn't conflict with ntpdate. Because chrony is a ntpdate replacement as well. ntpdate, thus, conflicts with chrony. -- .''`. Baloo [EMAIL PROTECTED]

Re: Speaking of ntp, yes CD-R does mess with the clock!

On Sun, Dec 22, 2002 at 06:46:50PM -0600, Adam Majer wrote: On Sun, Dec 22, 2002 at 10:32:43AM -0800, Bill Moseley wrote: On Sun, 22 Dec 2002, Shawn Lamson wrote: Maybe it's because the CD-R is so fast? Let's do the time warp again! This is why I installed rdate, I think it is b/c

Re: Speaking of ntp, yes CD-R does mess with the clock!

On Tue, 24 Dec 2002, Rob Weir wrote: I'd say this is the sort of thing people mean when people say 'IDE sucks!'; the CPU has to babysit the burner through the entire process... It's hard for me to believe that can be the only problem. The clock falls behind almost a minute during a 4 minute

Re: Speaking of ntp, yes CD-R does mess with the clock!

Bill Moseley writes: I just don't think it unreasonable that there could be periods of time when ntp can't connect to the remote hosts -- and that should not stop ntp. Chrony is designed to work with intermittent connections. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill

Re: Speaking of ntp, yes CD-R does mess with the clock!

On 24 Dec 2002, John Hasler wrote: Bill Moseley writes: I just don't think it unreasonable that there could be periods of time when ntp can't connect to the remote hosts -- and that should not stop ntp. Chrony is designed to work with intermittent connections. Any idea why it conflicts

Re: Speaking of ntp, yes CD-R does mess with the clock!

problems but cdrecord doesn't. I also noticed a similar effect recently when copying a large number of CDs to disk (several hundred), on a couple of occasions a timeout caused DMA to become disabled on the CDrom drive and when that happened the clock started running slow. James -- James Tappin

Re: Speaking of ntp, yes CD-R does mess with the clock!

is designed to work with intermittent connections. Any idea why it conflicts with ntpdate? Installing it remvoed ntpdate. ntp didn't conflict with ntpdate. No idea...chrony is a lot smarter than ntpdate though; it gradually moves your clock back and forth so that running apps don't get confused

Re: Speaking of ntp, yes CD-R does mess with the clock!

-- and that should not stop ntp. Chrony is designed to work with intermittent connections. Any idea why it conflicts with ntpdate? Installing it remvoed ntpdate. ntp didn't conflict with ntpdate. No idea...chrony is a lot smarter than ntpdate though; it gradually moves your clock back

Re: Speaking of ntp, yes CD-R does mess with the clock!

...chrony is a lot smarter than ntpdate though; it gradually moves your clock back and forth so that running apps don't get confused, as well as tracking how inaccurate your hardware RTC is, and fixing it while it drifts. Overall, a very cool tool. Maybe I missed this in the docs, but I didn't see

Re: Speaking of ntp, yes CD-R does mess with the clock!

. ntp didn't conflict with ntpdate. No idea...chrony is a lot smarter than ntpdate though; it gradually moves your clock back and forth so that running apps don't get confused, as well as tracking how inaccurate your hardware RTC is, and fixing it while it drifts. Overall, a very

Re: Speaking of ntp, yes CD-R does mess with the clock!

Bill Moseley writes: Any idea why [Chrony] conflicts with ntpdate? I didn't think it was a good idea to have two programs yanking on the system clock at the same time. As far as I know chronyc lets you do everything that ntpdate does. -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood

Re: clock timer configuration lost-problably via686a motherboard

No creo que pueda solucionarte el problema. Pero te comento lo que es el skew del reloj. Es un defecto de diseño de la placa madre. Se trata de un mal rutado del reloj. El reloj debe atacar a casi todos los circuitos al mismo tiempo, piensa que ha frecuencias muy grandes, enseguida se puede

Re: clock skew detected

compila el warning clock skew detected , para quien no sepa cual era el error que me aparece era este: probable hardware bug: clok time configuration lost- probably VIA686a motherboard probable hardware bug: restoring chip Puede tener relación

Re: clock timer configuration lost-problably via686a motherboard

On Saturday 21 December 2002 16:35, [EMAIL PROTECTED] wrote: Hola de nuevo, Gracias por contestar Aritz, lo del google ya lo probé y en todos los foros y listas dicen que no pueden solucionarlo nadie. Respecto a poner el kernel 2.4.18, lo he intentado, pero mi propósito es montar un pequeño

Re: Speaking of ntp, yes CD-R does mess with the clock!

On Sat, 21 Dec 2002 22:46:34 -0800 (PST) Bill Moseley [EMAIL PROTECTED] wrote: I had somene run: date; burn-cd.sh; date and burning the CD using cdrdao (48x drive -- about 4 minutes to burn a CD) caused the system clock to fall behind about *50* seconds. Maybe it's because the CD-R

Re: Speaking of ntp, yes CD-R does mess with the clock!

On Sun, 22 Dec 2002, Shawn Lamson wrote: date; burn-cd.sh; date and burning the CD using cdrdao (48x drive -- about 4 minutes to burn a CD) caused the system clock to fall behind about *50* seconds. Maybe it's because the CD-R is so fast? Let's do the time warp again

Re: Speaking of ntp, yes CD-R does mess with the clock!

On Sun, Dec 22, 2002 at 10:32:43AM -0800, Bill Moseley wrote: On Sun, 22 Dec 2002, Shawn Lamson wrote: date; burn-cd.sh; date and burning the CD using cdrdao (48x drive -- about 4 minutes to burn a CD) caused the system clock to fall behind about *50* seconds. Maybe it's

clock skew detected

warning clock skew detected , para quien no sepa cual era el error que me aparece era este: probable hardware bug: clok time configuration lost- probably VIA686a motherboard probable hardware bug: restoring chip Puede tener relación? alguien tiene idea

Re: clock skew detected

al hacer el make dep me sale en casi todas las lineas que compila el warning clock skew detected , para quien no sepa cual era el error que me aparece era este: probable hardware bug: clok time configuration lost- probably VIA686a motherboard

clock timer configuration lost-problably via686a motherboard

Hola de nuevo, Gracias por contestar Aritz, lo del google ya lo probé y en todos los foros y listas dicen que no pueden solucionarlo nadie. Respecto a poner el kernel 2.4.18, lo he intentado, pero mi propósito es montar un pequeño servidor y uso un pentium 100 Mhz, he modificado el kernel y al

Speaking of ntp, yes CD-R does mess with the clock!

I had somene run: date; burn-cd.sh; date and burning the CD using cdrdao (48x drive -- about 4 minutes to burn a CD) caused the system clock to fall behind about *50* seconds. Maybe it's because the CD-R is so fast? Let's do the time warp again! They are running testing with 2.4.18 and xfs

RE: Clock running slow

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 SCSI

Re: Clock running slow

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

Re: Clock running slow

clock running slow, the hwclock actually seems to be running a little *fast*. ;) -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Clock running slow - followup

on both machines at various points in time due to upgraded cd-rom writer drives. I had never made the association that that could have been a cause for the system clock to be running slow. I was unable to find the cause at the time. Cheers David On Wed, 04 Dec 2002 21:16:23 -0800 Bill

Re: Clock running slow

restarted for ten days. This is on an old Dell PIII machine. What steps should I follow to reset the clock (and hwclock)? Do I need to remove or reset a drift file? What could cause the clock to get that far behind while ntpd is running? I can see that ntp is running from ps, and I see

Re: Clock running slow

follow to reset the clock (and hwclock)? Do I need to remove or reset a drift file? What could cause the clock to get that far behind while ntpd is running? I can see that ntp is running from ps, and I see the drift file being written to (just a few minutes ago): $ ls -l /var/lib

Re: Clock running slow

. I just checked again and it's twenty minutes slow again. The machine has not been restarted for ten days. This is on an old Dell PIII machine. What steps should I follow to reset the clock (and hwclock)? Do I need to remove or reset a drift file? What could cause the clock to get that far

Re: Clock running slow

12.294 from /var/lib/ntp/ntp.drift Dec 4 21:42:31 burn ntpd[12292]: signal_no_reset: signal 17 had flags 400 Oh! and a few minutes later: Dec 4 21:46:00 burn ntpd[12291]: time correction of 1625 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. Well, that explains

Re: Clock running slow

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 have

Re: Clock running slow

. The machine is used for burning CDs and they are ide-scsi. Can you recommend a way to test this? Any work-arounds? Time is not critical on this machine -- I suppose I could just crontab ntpdate. Thanks James, Hum... So, how does cron keep from running things twice if the clock gets set back before

make[2]: warning: Clock skew detected. Your build may be incomplete.

Hallo zusammen, beim Kernelbau bekomm ich diese Meldung: ... make[3]: warning: Clock skew detected. Your build may be incomplete. make[3]: Leaving directory `/usr/src/linux-2.4.19/Documentation/DocBook' make[2]: warning: Clock skew detected. Your build may be incomplete. make[2]: Leaving

Re: make[2]: warning: Clock skew detected. Your build may beincomplete.

Am Don, 2002-11-28 um 17.39 schrieb Thorsten Schifferdecker: Hallo zusammen, beim Kernelbau bekomm ich diese Meldung: ... make[3]: warning: Clock skew detected. Your build may be incomplete. make[3]: Leaving directory `/usr/src/linux-2.4.19/Documentation/DocBook' make[2]: warning

Re: make[2]: warning: Clock skew detected. Your build may be incomplete.

Am 28.11.2002 17:39:16, Thorsten Schifferdecker schrieb: beim Kernelbau bekomm ich diese Meldung: ... make[3]: warning: Clock skew detected. Your build may be incomplete. [...] Was soll mir das sagen, Du hast die Zeit, da Dein Rechner mit Kompilieren beschaeftigt war, genutzt und

Re: Hardware clock Real time clock

On Sat, 9 Nov 2002, David Ulrich wrote: Hello, J'ai compilé mon kernel 2.4.18 pour mon PowerMac 9500MP avec l'option enhanced real time clock (elle est notée comme utile au multipro). Mais au boot, ça fige à: Setting the system clock using the hardware clock as reference... Et à

Re: Hardware clock Real time clock

clock (elle est notée comme utile au multipro). Mais au boot, ça fige à: Setting the system clock using the hardware clock as reference... Et à l'extinction à: Saving the system clock time to hardware clock... Est-ce une opton qui ne marche pas avec les ppc 604e? Ya t-il qqch à configurer? oui

Re: Hardware clock Real time clock

On Sun, 10 Nov 2002, David Ulrich wrote: J'ai compilé mon kernel 2.4.18 pour mon PowerMac 9500MP avec l'option enhanced real time clock (elle est notée comme utile au multipro). [SNIP] oui, ne pas se tromper entre CONFIG_PPC_RTC et CONFIG_RTC il faut CONFIG_PPC_RTC=y

Hardware clock Real time clock

Hello, J'ai compilé mon kernel 2.4.18 pour mon PowerMac 9500MP avec l'option enhanced real time clock (elle est notée comme utile au multipro). Mais au boot, ça fige à: Setting the system clock using the hardware clock as reference... Et à l'extinction à: Saving the system clock time

check clock system

ME aparece este mensage cuando intento compilar mplayer ! coloco ./configure y me larga error con ese mensaje. error check clock system(creo que algo asi) intente compilar lame, y tambien. que pasa como chequeo el reloj del sistema, por que es el error disculpen si la pregunta es tonta, estoy

Enhanced Real Time Clock Support?

Hello, In the kernel configuratioin, I found a description in the help page of SMP support. People using multiprocessor machines who say Y here should also say x x Y to Enhanced Real Time Clock Support, below. The Advanced Power x x Management code will be disabled if you say Y here

Re: Enhanced Real Time Clock Support?

also sprach Patrick Hsieh [EMAIL PROTECTED] [2002.06.25.1159 +0200]: People using multiprocessor machines who say Y here should also say x x Y to Enhanced Real Time Clock Support, below. The Advanced Power x y Management code will be disabled if you say Y here. Console Drivers

<    1   2   3   4   5   6   7   8   9   10   >