Bug 3930 - does not boot after changes in sendmail.cf/fails to execute linuxconf while booting
does not boot after changes in sendmail.cf/fails to execute linuxconf while b...
Status: CLOSED DUPLICATE of bug 3202
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
6.0
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-07-07 03:01 EDT by skopp
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-03 15:21:38 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)

  None (edit)
Description skopp 1999-07-07 03:01:55 EDT
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 12:29:59 EDT
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 15:21:59 EDT
*** This bug has been marked as a duplicate of 3202 ***

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