Bug 3225 - Hostname doesn't get changed when linuxconf switches system profiles
Hostname doesn't get changed when linuxconf switches system profiles
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
6.0
i386 Linux
medium Severity low
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-06-02 21:31 EDT by Adam Spiers
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-07-13 12:08:21 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 Adam Spiers 1999-06-02 21:31:37 EDT
If you use linuxconf to switch system profiles to a profile
with a different hostname, all it does is archive the old
config files and extract the new ones.  This means that
if you enable the askrunlevel feature of linuxconf, and
ask to switch profile at boot-time, by the time all the
startup scripts have completed, you end up with a machine
whose current hostname doesn't match the current system
profile.  Clearly this can then cause problems with
networking.

You may well decide to ignore this bug on the grounds that
Redhat doesn't "do" askrunlevel by default, in which case I
guess I'll just report it to the linuxconf guys.
Comment 1 Jay Turner 1999-06-29 07:17:59 EDT
This issue has been forwarded to a developer for further action.
Comment 2 Michael K. Johnson 1999-07-13 12:08:59 EDT
You are correct; our answer is in fact that we don't do
askrunlevel by default.  However, I have sent this bug
report to Jacques Gelinas by adding him to the CC line,
so he can look into it himself and decide what to do about
it.

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