Bug 3458 – hwclock --adjust (ie. boot) hangs

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 3458 - hwclock --adjust (ie. boot) hangs

Summary:	hwclock --adjust (ie. boot) hangs

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	util-linux (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jay Turner
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-06-14 12:35 EDT by jes.sorensen
Modified:	2015-01-07 18:37 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-06-14 12:58:26 EDT
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 jes.sorensen 1999-06-14 12:35:35 EDT

If one by accident gets the system clock set to some time
far out in the future, boots the system (thus having
/sbin/hwclock --adjust run by /etc/rc.d/rc.sysinit), then
reboots and sets the clock back using the BIOS. After this
the system will hang at boot time when hwclock --adjust
tries to wait several years to catch up on the time.

Comment 1 Jeff Johnson 1999-06-14 12:58:59 EDT

And you expect the software to do what? :-)

------- Additional Comments From   06/14/99 13:07 -------
I expect it to detect that it is about to wait for ages and let the
user know, ideally it should print a warning message if it believes it
is about to wait for more than say 1 minute.

I can solve this kind of problem myself, but to be frank, I doubt that
the average user will be able to figure out what is wrong and fix it.
I am sure your support people will love trying to figure out the
problem if they get a customer calling on this one.

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