Bug 58414 – RTC will be corrupted.

Bug 58414 - RTC will be corrupted.

Summary:	RTC will be corrupted.

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	initscripts (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-01-16 00:51 EST by Erhard Kiefner
Modified:	2014-03-16 22:25 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-01-29 16:32:54 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Erhard Kiefner 2002-01-16 00:51:50 EST

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0; Customized 
5.00.2314.1003)

Description of problem:
There is a bug in the .../init.d/halt script of Red Hat 7.1/7.2. The system 
time will be written back to the RTC during each shutdown or reboot. That's a 
bug because the system time isn't accurate. The RTC will be corrupted. You have 
to comment out the line with the hwclock command. 

Our experience: The RTC of modern PCs and servers is very exact but the system 
time already differs after a short time from the real time.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Set the RTC within the BIOS setup.
2.Boot Red Hat Linux 7.1/7.2.
3.Change the system time so that's different from RTC.
4.Shutdown the system.
5.Check the RTC within the BIOS setup. It's coruupted!
	

Additional info:

Comment 1 Elliot Lee 2002-01-29 16:14:54 EST

This is an initscripts issue.

Comment 2 Bill Nottingham 2002-01-29 16:32:48 EST

How did you change the time?

Also, in what way is it 'corrupted'?

Comment 3 Bill Nottingham 2002-11-25 16:56:34 EST

closing, no response

Note You need to log in before you can comment on or make changes to this bug.