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

Bug 3930

Summary:	does not boot after changes in sendmail.cf/fails to execute linuxconf while booting
Product:	[Retired] Red Hat Linux	Reporter:	skopp
Component:	linuxconf	Assignee:	Michael K. Johnson <johnsonm>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	jack
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:	1999-08-03 19:21:38 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 skopp 1999-07-07 07:01:55 UTC

Have used linuxconf to change sendmail.cf.
Have a LAN with inofficial FQDN an so I need the "Dj"
command in sendmail.cf to fake my FQDN due to ISP
requirements.  So I did changes on sendmail.cf by hand
because linuxconf did not set any "Dj" command in
sendmail.cf (which is a different issue, I know).
On next reboot, the systems stucks while
executing /etc/rc.d/rc3.d/S99linuxconf !
If you boot in "single" mode and execute S99linuxconf you
see why: S99linuxconf needs manual input because the
sendmail.cf was changed by hand!

Workaround: have renamed S99linuxconf to orig-S99linuxconf

Comment 1 Michael K. Johnson 1999-07-30 16:29:59 UTC

Jacques, is this fixed in 1.16r1.3?  This seems to stir a faint
memory of discussion on the linuxconf list...

Comment 2 Derek Tattersall 1999-08-03 19:21:59 UTC

*** This bug has been marked as a duplicate of 3202 ***