On Nov 28, 2007 4:30 PM, Nathan Stien <<a href="mailto:nathanism@gmail.com">nathanism@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The machine has mysteriously lost the ability to resolve its own<br>hostname. This is a problem because sudo for whatever reason needs to<br>resolve the hostname in order to let me do anything. This machine has<br>an ubuntu-style setup with respect to sudo -- the root account is
<br>locked. I can't just "su root".<br><br>OK, I says to myself, I'll just add the hostname to /etc/hosts and<br>move on with life.<br><br>nathan@lildeb:~$ sudo vi /etc/hosts<br>sudo: unable to resolve host lildeb
<br><br>Ohhhhh, yeeeaaahhh. D'oh.<br></blockquote></div><br clear="all">I'd have done it the same way you did. Did you figure out what the problem was? Did you delete the 127... line from /etc/hosts or mess up /etc/nsswitch.conf?
<br><br>If I were in a position where rebooting was absolute last resort, I'd probably try and figure out how name resolution was being done and then find some way to make it work the way sudo wanted.<br><br>Maybe I'd try and unplug the ethernet cable to see if that affects anything. Too bad the system's fixed now. :-)
<br>-- <br>Matthew Nuzum<br>newz2000 on freenode