unresolvable hostname breaks system
Bug #197494 reported by
Cody A.W. Somerville
This bug report is a duplicate of:
Bug #32906: sudo fails if it cannot resolve the local hostname and no MTA is installed.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| hostname (Ubuntu) |
Incomplete
|
Wishlist
|
Unassigned | ||
| sudo (Ubuntu) |
Incomplete
|
Wishlist
|
Unassigned | ||
Bug Description
If the current host name set for the system is not resolvable (generally there is a static entry in /etc/hosts), than several components of the Ubuntu system will cease to function (such as sudo and reportedly X). If the user used the host name command to set a new host name, they only have to reboot to have their old host name loaded from /etc/hostname. However, if they modify /etc/hostnanme than the user will have to boot into the recovery mode (which provides a root shell) to either change /etc/hostname to one that resolves or add an entry to /etc/hosts to route the host name to localhost (127.0.0.1).
Would it be possible to have the current host name always be able to resolve to localhost?
Revision history for this message
| Ralph Janke (txwikinger) wrote | #1 |
| Changed in hostname: | |
| importance: | Undecided → Wishlist |
| status: | New → Incomplete |
| Changed in sudo: | |
| importance: | Undecided → Wishlist |
| status: | New → Incomplete |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
Revision history for this message
| Neal McBurnett (nealmcb) wrote | #3 |
To post a comment you must log in.
Thanks for your report. Your idea might get more attention and have the possibility of being implemented if you submit a specification for it. First check whether the idea is already registered <https:/
specification's drafter about your ideas. Otherwise, you can start writing a spec yourself. <https:/