Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 48980

Summary:	Bombs out when starting up on line 387
Product:	[Retired] Red Hat Linux	Reporter:	John Strange <john>
Component:	ksconfig	Assignee:	Brent Fox <bfox>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-07-18 20:30:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Strange 2001-07-12 20:13:55 UTC

Description of Problem:

During installation, the /etc/sysconfig/clock file did not seem to be 
created, so it got messed up on this file not being there.  I created the 
file from a 7.1 installation and it then bombed out on line 387, which 
when commented out it worked fine.  I don't know python well enough to 
troublshoot it though.

Comment 1 Glen Foster 2001-07-13 19:47:46 UTC

This defect considered MUST-FIX for Fairfax gold-release.

Comment 2 Brent Fox 2001-07-18 20:30:37 UTC

I have fixed the problem with the installer not creating the
/etc/sysconfig/clock file.  However, it would be helpful if you could attach the
traceback that you saw as well as your /etc/sysconfig/clock file that you copied
from the 7.1 system.

Comment 3 Brent Fox 2001-07-25 02:27:55 UTC

I have fixed the installer such that it writes out a /etc/sysconfig/clock file.
 I have also fixed ksconfig such that it will not crash in the event that
/etc/sysconfig/clock file doesn't exist.  Thanks for your report.