#320 closed defect (fixed)
Get rid of bad entry in /etc/hosts with dhcp client
| Reported by: | DJ Lucas | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BOOK | Version: | ~CVS |
| Severity: | normal | Keywords: | VERIFIED |
| Cc: |
Description
/etc/hosts most likely has an incorrect IP address for the FQDN of the local machine. Suggest a script that updates /etc/hosts with corrected IP.
Attachments (6)
Change History (25)
by , 23 years ago
| Attachment: | bootscripts.xml added |
|---|
by , 23 years ago
| Attachment: | dhcp-hosts.patch added |
|---|
patch to BLFS/BOOK/connect/dhcp/bootscripts.xml
comment:1 by , 23 years ago
| attachments.isobsolete: | 0 → 1 |
|---|
comment:2 by , 23 years ago
| Milestone: | future → post-1.0 |
|---|---|
| Priority: | lowest → normal |
| Severity: | enhancement → normal |
by , 23 years ago
| Attachment: | dhcp-hosts.2.patch added |
|---|
Uses output of 'ifconfig eth0' to correct the hosts file
comment:3 by , 23 years ago
| attachments.isobsolete: | 0 → 1 |
|---|
by , 23 years ago
| Attachment: | dhcp-hosts-fix-2.patch added |
|---|
forgot to copy the original file and edit.
comment:4 by , 23 years ago
| attachments.isobsolete: | 0 → 1 |
|---|
comment:5 by , 23 years ago
Is this bug really needed? The resolution of a DHCP address should be done by the ISP issuing the IP address through the DNS system. Anything else is a workaround. This probably should be a hint and not a candidate for the book.
comment:6 by , 23 years ago
| Resolution: | → later |
|---|---|
| Status: | new → closed |
The problem need additional investigation. Is something else 'not right'? i.e. XFree looking to /etc/host for FQDN instead of gethostname() [be sure and laugh if gethostname() resolves through /etc/host].
comment:7 by , 23 years ago
| Milestone: | post-1.0 → 6.0 |
|---|---|
| Resolution: | later |
| Status: | closed → reopened |
5.0 is out, reopen all bugs.
comment:8 by , 23 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → new |
comment:9 by , 23 years ago
| Status: | new → assigned |
|---|
comment:10 by , 23 years ago
We need to take a quick look at this and see what's up (somebody who would know more than I). A quick recap. I discovered this 'issue' by mistyping my hostname in /etc/hosts. X must look at /etc/hosts for the hostname and/or ip address. I've not looked into this very deeply so I don't yet know if it really makes a difference. My simple testcase was mistyping the hostname and then do a startx and check the log. I haven't seen any problems with X getting the wrong IP address from that lookup. Being that we've been using it this way for a long time...It's probably not a real problem, but I thought it should be corrected anyways. I'll look into it furthur myself when I get to a point where I can kill all of these xterms...say maybe in like two weeks ;-)
-- DJ
comment:11 by , 22 years ago
Other possible fix as discussed here: http://archive.linuxfromscratch.org/mail-archives/blfs-dev/2003-November/004562.html
Probably much better that the other. Actual commit pending discussion on blfs-dev.
comment:12 by , 22 years ago
| attachments.isobsolete: | 0 → 1 |
|---|
comment:13 by , 22 years ago
| Summary: | Make ifup-eth0 in dhcp client correct /etc/hosts file. → Get rid of bad entry in /etc/hosts with dhcp client |
|---|
comment:14 by , 22 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
comment:15 by , 22 years ago
| attachments.isobsolete: | 0 → 1 |
|---|
comment:16 by , 22 years ago
| Status: | new → assigned |
|---|
comment:17 by , 22 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:18 by , 22 years ago
| Keywords: | VERIFIED added |
|---|
rough suggestion (may be useable as is)