It seems my cmos battery is going down and each time I boot to suse or legacy the time gets hosed. Is there a script for looking up the time online and setting the clock? Should it be called in /etc/init.d/boot.local ?? So that it does not matter which user or root signs onto the box?? CWSIV ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!
On Monday 27 October 2003 02:25, Carl William Spitzer IV wrote:
It seems my cmos battery is going down and each time I boot to suse or legacy the time gets hosed.
Network Time Protocol daemon will do this : XNTP program Because the Date must be correct, and the Time must be approx right for xntpd to operate, I believe you need to Manually set Date & Time using < date -s > upon reboot Because changing the date with date -s will probably trigger CRON to run various routines, maybe it is a good idea to Kill -9 the CRON daemon before setting < date -s > ~ find the cron process number by doing :- ps aux | grep cron After setting date and time, remember to restart cron by running :- /usr/sbin/cron ................................... best wishes ____________ sent on Linux ____________
On Monday 27 October 2003 2:25 am, Carl William Spitzer IV wrote:
It seems my cmos battery is going down and each time I boot to suse or legacy the time gets hosed.
Is there a script for looking up the time online and setting the clock?
Have you tried a new battery, the time is not the only data stored in nvram.
The 03.10.26 at 18:25, Carl William Spitzer IV wrote:
It seems my cmos battery is going down and each time I boot to suse or legacy the time gets hosed.
Is there a script for looking up the time online and setting the clock?
Yes, there is; simply configure /etc/ntp.conf But change your battery FAST! You will loose many things if you don't: the battery is used to maintain the bios configuration in the cmos memory. Your computer may even not boot if you don't replace it, and leaking chemicals from a spent battery could destroy your motherboard. -- Cheers, Carlos Robinson
This is a PII box and the MB book does not indicate all the special
messages you suggest.
Second all the behaviors were the same as those I observed in a 486 when
its CMOS battery went down.
My experience led me into the same wrong path so dont feel put upon
because I asked questions considtant with my experience.
I stumbled upon the type of time setting when I was studying hardware
settings trying to resolve internet and email issues. As I had mislaid
my books I decided to change something and see if it helped or hurt my
system. the next day when I found my books and booted the system things
worked correctly.
I dont expect anyone here to apologise for asking for help while
continuing to hack arround their system to fix problems. Thats how we
grow linux and get smarter ourselves. That said I did not intend to
waste anyones time; only to solve a problem.
CWSIV
On Wed, 29 Oct 2003 14:17:53 +0100 (CET) "Carlos E. R."
El 2003-10-28 a las 20:40, Carl William Spitzer IV escribió:
I plan to have it onhand for the switch. I multiboot with win311 and have cmos backedup with Norton Rescue. I also found the time was set to utc and I switched it to local time. Now it seems to leave the clock alone and booting to win3 and the time is correct today.
You didn't explain that before.
If the battery is bad, which is what you said, there is a message from the BIOS when you boot that says that the battery is bad and that you must replace it. There is no possible mistake in reading that message.
If the battery runs low, the CMOS configuration will be cleared and reset, and you also get a very clear message about it.
Now what you say is that the time was simply set wrong -- that is a very different issue, and a known one when you boot both into Linux and windows on the same machine, and has nothing to do with the battery.
Please, when you email to the list, please be careful and precise about what you write and don't point us on the wrong direction!
-- Saludos Carlos Robinson
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!
The 03.10.29 at 18:24, Carl William Spitzer IV wrote:
This is a PII box and the MB book does not indicate all the special messages you suggest.
Second all the behaviors were the same as those I observed in a 486 when its CMOS battery went down.
My experience led me into the same wrong path so dont feel put upon because I asked questions considtant with my experience.
I'm sorry; perhaps I was too harsh. But try this, if you want to experiment one day: with the computer powered off, remove the battery for a minute, or put the jumper in the reset cmos position for a second if it is not of the removable type. You will see when you boot a message of the bios saying that the CMOS memory was corrupt and reset to sensible values. If you remove the battery completely, the message will say that the battery is bad, and replace it. This has been the behavior since... who knows, from the 386 or earlier. Certainly earlier, I have an 8086 that does this. But... if you say that it happened to you some other time, that the battery was low and the clock drifted, without a warning message during boot... well, I accept that could happen. :-) Bad design. :-(
I stumbled upon the type of time setting when I was studying hardware settings trying to resolve internet and email issues. As I had mislaid my books I decided to change something and see if it helped or hurt my system. the next day when I found my books and booted the system things worked correctly.
I dont expect anyone here to apologise for asking for help while continuing to hack arround their system to fix problems. Thats how we grow linux and get smarter ourselves. That said I did not intend to waste anyones time; only to solve a problem.
Sorry again. But please, try to explain your problems better: I have tried several times to answer to your queries, but I don't get a clear picture of what you are asking. It may be me, but :-? it seems that sometimes you contradict yourself. -- Cheers, Carlos Robinson
participants (4)
-
Carl William Spitzer IV
-
Carlos E. R.
-
david stevenson
-
pinto