On Wed, 2004-12-08 at 15:02, James Knott wrote:
Kelly J. Morris wrote:
Thanks. I think (hope) I'm OK now after re-setting YaST again. But, I'd like to try ntp. There are a bunch of ntp folders on my system (9.0 Pro) but they are all empty. Where can I find ntp? Kelly
Go into Yast, Network Services > NTP Client. You can find a list of ntp servers at http://ntp.isc.org/bin/view/Servers/WebHome.
James - Before I could do much with NTP, I booted up this morning to find yet another new date and time on my system. I'm puzzled as to what could be causing this. Each time, I go into YaST under "clock and time zone configuration" and re-set everything, only to have it boot with incorrect time and date at the next boot-up. I remember from the ancient days of DOS that a similar behavior was due to a need to replace a battery on the motherboard. Could this also be a hardware issue? It's a P4 2.8 Ghz and only 12 months old. TIA Kelly Morris
On Thu, 09 Dec 2004 11:20:26 -0500, Kelly J. Morris
On Wed, 2004-12-08 at 15:02, James Knott wrote:
Kelly J. Morris wrote:
Thanks. I think (hope) I'm OK now after re-setting YaST again. But, I'd like to try ntp. There are a bunch of ntp folders on my system (9.0 Pro) but they are all empty. Where can I find ntp? Kelly
Go into Yast, Network Services > NTP Client. You can find a list of ntp servers at http://ntp.isc.org/bin/view/Servers/WebHome.
James - Before I could do much with NTP, I booted up this morning to find yet another new date and time on my system. I'm puzzled as to what could be causing this. Each time, I go into YaST under "clock and time zone configuration" and re-set everything, only to have it boot with incorrect time and date at the next boot-up.
I remember from the ancient days of DOS that a similar behavior was due to a need to replace a battery on the motherboard. Could this also be a hardware issue? It's a P4 2.8 Ghz and only 12 months old.
TIA Kelly Morris
Kelly, to check if this is hardware issue, check the date/time in your BIOS setup. When you prepare to shutdown for the night, reboot, and hit F2, or Del, or whatever button is for entering the BIOS setup. There you will see the current time set for the system in the CMOS clock. Shutdown. In the morning, before you boot the OS, do it again. If time differs, than for sure this is hardware problem. Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
On Thu, 2004-12-09 at 11:38, Sunny wrote:
James - Before I could do much with NTP, I booted up this morning to find yet another new date and time on my system. I'm puzzled as to what could be causing this. Each time, I go into YaST under "clock and time zone configuration" and re-set everything, only to have it boot with incorrect time and date at the next boot-up.
I remember from the ancient days of DOS that a similar behavior was due to a need to replace a battery on the motherboard. Could this also be a hardware issue? It's a P4 2.8 Ghz and only 12 months old.
TIA Kelly Morris
Kelly, to check if this is hardware issue, check the date/time in your BIOS setup. When you prepare to shutdown for the night, reboot, and hit F2, or Del, or whatever button is for entering the BIOS setup. There you will see the current time set for the system in the CMOS clock. Shutdown. In the morning, before you boot the OS, do it again. If time differs, than for sure this is hardware problem.
Sunny
Sunny - Thanks very much. Will do. Kelly
Kelly, On Thursday 09 December 2004 08:20, Kelly J. Morris wrote:
...
James - Before I could do much with NTP, I booted up this morning to find yet another new date and time on my system. I'm puzzled as to what could be causing this. Each time, I go into YaST under "clock and time zone configuration" and re-set everything, only to have it boot with incorrect time and date at the next boot-up.
I remember from the ancient days of DOS that a similar behavior was due to a need to replace a battery on the motherboard. Could this also be a hardware issue? It's a P4 2.8 Ghz and only 12 months old.
There is (almost certainly) a battery on your mainboard specifically so as to maintain the CMOS clock chip. Although it should last much longer than 12 months, it could actually be older than the 12 months you've owned the system. How do you power down? Do you turn of the switch on the power supply or on the power strip or unplug the system? If so, you force your system to rely on the battery for clock chip power. If, on the other hand, you just perform a soft power-down, then on at least some systems there is still some power supplied to your mainboard so that the soft power-up can operate and usually this power is available to the clock chip, too.
TIA Kelly Morris
Randall Schulz
On Thu, 2004-12-09 at 11:49, Randall R Schulz wrote:
Kelly,
On Thursday 09 December 2004 08:20, Kelly J. Morris wrote:
...
James - Before I could do much with NTP, I booted up this morning to find yet another new date and time on my system. I'm puzzled as to what could be causing this. Each time, I go into YaST under "clock and time zone configuration" and re-set everything, only to have it boot with incorrect time and date at the next boot-up.
I remember from the ancient days of DOS that a similar behavior was due to a need to replace a battery on the motherboard. Could this also be a hardware issue? It's a P4 2.8 Ghz and only 12 months old.
There is (almost certainly) a battery on your mainboard specifically so as to maintain the CMOS clock chip. Although it should last much longer than 12 months, it could actually be older than the 12 months you've owned the system.
Russell -
How do you power down? Do you turn of the switch on the power supply or on the power strip or unplug the system?
The only time I switch off is when my system locks up on me and I have to do a forced shutdown and cold reboot. Not often, but it happens.
If so, you force your system to rely on the battery for clock chip power. If, on the other hand, you just perform a soft power-down, then on at least some systems there is still some power supplied to your mainboard so that the soft power-up can operate and usually this power is available to the clock chip, too.
I almost always do a soft shutdown. Lucky for me, my computer vendor is just a few blocks away, so if nothing else works, I'll take my computer in for a battery change. I seem to remember that the batteries that needed to be soldered to the board have long-since been replaced by "watch batteries." Thanks. Kelly
On Thursday 09 December 2004 10:20 am, Kelly J. Morris wrote:
James - Before I could do much with NTP, I booted up this morning to find yet another new date and time on my system. I'm puzzled as to what could be causing this. Each time, I go into YaST under "clock and time zone configuration" and re-set everything, only to have it boot with incorrect time and date at the next boot-up.
I remember from the ancient days of DOS that a similar behavior was due to a need to replace a battery on the motherboard. Could this also be a hardware issue? It's a P4 2.8 Ghz and only 12 months old.
TIA Kelly Morris
Another thing to check is localtime vs UTC in YaST, System, Date & Time. IF you have multi-boot and boot into Windows most systems require that you use localtime to keep the system time consistent between Windows and Linux boots. This is very true on my system even if I never boot to Windows these days. All I have to do is boot Windows once a year and my clock is off IF I don't have YaST set to localtime. On other systems it does not seem to make a difference. Just another thing to check and YMMV. Stan
On Thu, 2004-12-09 at 12:50, Stan Glasoe wrote:
On Thursday 09 December 2004 10:20 am, Kelly J. Morris wrote:
James - Before I could do much with NTP, I booted up this morning to find yet another new date and time on my system. I'm puzzled as to what could be causing this. Each time, I go into YaST under "clock and time zone configuration" and re-set everything, only to have it boot with incorrect time and date at the next boot-up.
I remember from the ancient days of DOS that a similar behavior was due to a need to replace a battery on the motherboard. Could this also be a hardware issue? It's a P4 2.8 Ghz and only 12 months old.
TIA Kelly Morris
Another thing to check is localtime vs UTC in YaST, System, Date & Time. IF you have multi-boot and boot into Windows most systems require that you use localtime to keep the system time consistent between Windows and Linux boots. This is very true on my system even if I never boot to Windows these days. All I have to do is boot Windows once a year and my clock is off IF I don't have YaST set to localtime. On other systems it does not seem to make a difference. Just another thing to check and YMMV.
Stan
Stan - This is good to know. I always set to local time (I think). I have two hard drives and dual boot system with Windoze XP SP2. I'll make a special effort to be careful about setting in local time. Thanks. Kelly
On Thu, 2004-12-09 at 12:50, Stan Glasoe wrote:
On Thursday 09 December 2004 10:20 am, Kelly J. Morris wrote:
James - Before I could do much with NTP, I
Another thing to check is localtime vs UTC in YaST, System, Date & Time. IF you have multi-boot and boot into Windows most systems require that you use localtime to keep the system time consistent between Windows and Linux boots. This is very true on my system even if I never boot to Windows these days. All I have to do is boot Windows once a year and my clock is off IF I don't have YaST set to localtime. On other systems it does not seem to make a difference. Just another thing to check and YMMV.
Stan
Stan - This is good to know. I always set to local time (I think). I have two hard drives and dual boot system with Windoze XP SP2. I'll make a special effort to be careful about setting in local time. Thanks. Kelly
I would recommend using date and hwclock commands combination instead of YaST. It seems that YaST updates the current time for the current boot only and does not update hardware clock on your motherboard. That's why you lose your settings every time you reboot. Dmitry
--
On Thu, 2004-12-09 at 14:30, Dimych wrote:
On Thu, 2004-12-09 at 12:50, Stan Glasoe wrote:
On Thursday 09 December 2004 10:20 am, Kelly J. Morris wrote:
James - Before I could do much with NTP, I
Another thing to check is localtime vs UTC in YaST, System, Date & Time. IF you have multi-boot and boot into Windows most systems require that you use localtime to keep the system time consistent between Windows and Linux boots. This is very true on my system even if I never boot to Windows these days. All I have to do is boot Windows once a year and my clock is off IF I don't have YaST set to localtime. On other systems it does not seem to make a difference. Just another thing to check and YMMV.
Stan
Stan - This is good to know. I always set to local time (I think). I have two hard drives and dual boot system with Windoze XP SP2. I'll make a special effort to be careful about setting in local time. Thanks. Kelly
I would recommend using date and hwclock commands combination instead of YaST. It seems that YaST updates the current time for the current boot only and does not update hardware clock on your motherboard. That's why you lose your settings every time you reboot.
Dmitry
Dmitry - Thanks very much - I remembered "date" had forgotten about "hwclock." Also, what about "setclock' - what does that do? Kelly
* Kelly J. Morris
Also, what about "setclock' - what does that do?
/usr/sbin/setclock --help Usage: setclock [DATE/TIME] Sets both system time and hardware clock simultaneously. DATE resp. TIME resp. both must be specified according to the syntax of the program /bin/date. See "date --help" or "man 1 date" for details! now, that wasn't too awfully hard. *Please*, trim your quotes. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Thu, 2004-12-09 at 15:00, Patrick Shanahan wrote:
*Please*, trim your quotes.
Patrick - My personal preference is to trim quotes. Since 1995, I subscribe to 35 or 40 lists and am List Owner of 3. To my surprise, I've found that lots of folks object to trimming quotes. There are a number of reasons that they give, but the primary one is that it makes it more difficult for someone to "jump in" in the middle of a discussion and at the same time stay on-topic and avoid repetition. I don't agree, but I see their POV, especially if their e-mail client does not thread messages effectively. For example, I use Evolution but it only allows threading based on responses to a particular message, rather than threading based on "subject." So, I turned threading off in Evolution. PMMail for OS/2 Warp, however, has a terrific threading function, in addition to being a better all-around e-mail client than Evolution. So, if trimming quotes is "de rigeur" on this list, I'll gladly trim. Wish I could trim myself as easily as I can trim a message but that's another story ... Kelly
* Kelly J. Morris
Patrick - My personal preference is to trim quotes.
Appreciated. *Was* a standard expectation, but then there was aol, and the masses followed.
Since 1995, I subscribe to 35 or 40 lists and am List Owner of 3. To my surprise, I've found that lots of folks object to trimming quotes.
Of course there are those who object to the posted speed limits, parliamentary procedure, courtesy, ......
There are a number of reasons that they give, but the primary one is that it makes it more difficult for someone to "jump in" in the middle of a discussion and at the same time stay on-topic and avoid repetition.
Probably, they should have a good handle on the thread or shouldn't be jumping in. No reason for the majority who follow the list to have to suffer because someone else cannot be bothered.
I don't agree, but I see their POV, especially if their e-mail client does not thread messages effectively.
I also do not agree, but I do *not* see their POV.
For example, I use Evolution but it only allows threading based on responses to a particular message, rather than threading based on "subject." So, I turned threading off in Evolution. PMMail for OS/2 Warp, however, has a terrific threading function, in addition to being a better all-around e-mail client than Evolution.
change to mutt.
So, if trimming quotes is "de rigeur" on this list, I'll gladly trim.
Don't know about "de rigeur" for *any* list, but common courtesy for *all* lists. http://www.netmeister.org/news/learn2quote.html
Wish I could trim myself as easily as I can trim a message but that's another story ...
You say what you feel is necessary to make your point. gud luk, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Dimych wrote:
I would recommend using date and hwclock commands combination instead of YaST. It seems that YaST updates the current time for the current boot only and does not update hardware clock on your motherboard. That's why you lose your settings every time you reboot.
Actually, the system halt script (/etc/init.d/halt) updates the hardware clock from the system clock, every time the system shuts down (which includes rebooting, since it uses the same script).
The Thursday 2004-12-09 at 11:20 -0500, Kelly J. Morris wrote:
James - Before I could do much with NTP, I booted up this morning to find yet another new date and time on my system. I'm puzzled as to what could be causing this. Each time, I go into YaST under "clock and time zone configuration" and re-set everything, only to have it boot with incorrect time and date at the next boot-up.
This is a very frequent question. Quick answer: Make sure timezone configuration is correct (yast). Then set up the clock, as root, using a console. Forget kde. date --set=STRING (see man) date (to check it is correct) hwclock --systohc rm /etc/adjtime Detailed answer: http://susefaq.sourceforge.net/howto/time.html As for "setclock", it comes with package "shtools". Not a default package. If still having problems, are you double booting? -- Cheers, Carlos Robinson
On Thu, 2004-12-09 at 20:22, Carlos E. R. wrote:
This is a very frequent question. Quick answer:
Make sure timezone configuration is correct (yast).
Done
Then set up the clock, as root, using a console. Forget kde.
Carlos - I qualify as a certified CLI idiot. I can't seem to get the syntax of the new date and time correctly (which I assume replaces STRING below). I've tried man and howto and, while there are explanations, there are no examples and at my (subterranean) level, that's what I need.
date --set=STRING (see man) date (to check it is correct) hwclock --systohc rm /etc/adjtime
TIA Kelly Morris
--- "Kelly J. Morris"
I can't seem to get the syntax of the new date and time correctly (which I assume replaces STRING below). I've tried man and howto and, while there are explanations, there are no examples and at my (subterranean) level, that's what I need.
date --set=STRING (see man) date (to check it is
correct)
hwclock --systohc rm /etc/adjtime
TIA Kelly Morris
As a root user do: #date 12101000 (which means Dec, 10 10:00am, July 4th 2:15pm will be 07041415) #hwclock --systohc And you should be all set :) Dmitry
On Fri, 2004-12-10 at 10:05, Dimych wrote:
As a root user do: #date 12101000 (which means Dec, 10 10:00am, July 4th 2:15pm will be 07041415) #hwclock --systohc
Dimitry - Thanks. From what Carlos wrote, I thought that I had to use #date --set=12101000 rather than #date --set 12101000 That is, I thought "date" was to obtain the current date & time and "date --set" was to set the new date and time. Kelly
The Friday 2004-12-10 at 09:55 -0500, Kelly J. Morris wrote:
Then set up the clock, as root, using a console. Forget kde.
Carlos - I qualify as a certified CLI idiot. I can't seem to get the syntax of the new date and time correctly (which I assume replaces STRING below). I've tried man and howto and, while there are explanations, there are no examples and at my (subterranean) level, that's what I need.
You are absolutely correct, some man pages are good examples of how not to write user documentation :-p I also stumbled time ago with that one, and found the correct string by trial and error; but I forgot to write it up at the time, so I did not mail them when I told you to use date and read the man page. I forgot that "detail", sorry.
date --set=STRING (see man)
Looking again at that man page, I find this other syntax is easier: date [-u|--utc|--universal] [MMDDhhmm[[CC]YY][.ss]] as long as I don't have to state the year, then "I" have problems as well. Let me see... ouch, don't try this, linux dislikes you touching the clock and has weird effects (cron gets very "pissed", for example). nimrodel:~ # date --iso --set=2005-12-11 2005-12-11 nimrodel:~ # date Sun Dec 11 00:00:05 CET 2005 nimrodel:~ # date --iso --set=2004-12-11 2004-12-11 nimrodel:~ # date Sat Dec 11 00:00:03 CET 2004 Ouch, I intentended to modify the date, not time. Time got reset to 00:00. nimrodel:~ # date --iso --set="2004-12-11 01:21" 2004-12-11 nimrodel:~ # date -u Sat Dec 11 00:21:18 UTC 2004 nimrodel:~ # rccron restart Shutting down CRON daemon done Starting CRON daemon done nimrodel:~ # rm /etc/adjtime -- Cheers, Carlos Robinson
On Thu, 2004-12-09 at 20:22, Carlos E. R. wrote:
Make sure timezone configuration is correct (yast). Then set up the clock, as root, using a console. Forget kde.
date --set=STRING (see man) date (to check it is correct) hwclock --systohc rm /etc/adjtime
As a followup, let me report that I did the following: date 12101000 hwclock --systohc rm /etc/adjtime and now everything works fine. I booted into Windoze several times, too, to see if that would affect the date and/or time. It didn't, so far ... Thanks to all who helped. Kelly
participants (8)
-
Carlos E. R. -
Darryl Gregorash -
Dimych -
Kelly J. Morris -
Patrick Shanahan -
Randall R Schulz -
Stan Glasoe -
Sunny