Bug 392691
Summary: | ifup-post setups hostname with no user option controlling it | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Dan Fruehauf <dan> | ||||
Component: | initscripts | Assignee: | initscripts Maintenance Team <initscripts-maint-list> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 5.1 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-11-20 17:16:39 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: | |||||||
Attachments: |
|
Description
Dan Fruehauf
2007-11-20 16:46:33 UTC
Created attachment 265101 [details]
Patch to network-functions to enable the NEED_HOSTNAME flag
Why would you want to keep a localhost hostname? My case is configuring a computer with certain settings. Then later connecting it to the Internet and suddenly getting a new hostname. Some applications / settings which depended on it failed to run. I believe that this unexpected / surprising hostname change is somewhat problematic. Besides, the suggested patch does not interfere with any other behavior which is currently implemented. This is expected behavior in pretty much every release since the old Red Hat Linux days - if a static hostname is expected, just setting it to something other than localhost should do the trick. Expected behavior is preserved but more flexibility is added. I would like to keep a localhost.localdomain hostname regardless of what's happening. It's not that awkward. |