Comment 49 for bug 32906
Revision history for this message
| Pasi (pasi-lehtimaki) wrote Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on | #49 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I encountered this same problem after upgrading from gutsy to hardy. After trying to resolve connection problems which were messed up after the upgrade the sudo stopped working. It happened when I disabled my wireless and lan connection from kde network management tools. Booting in recovery mode and adding the host name back did fix the problem.
I find this very serious problem since ubuntu relies so heavily on sudo (the lack of root account) and if that command fails there is no way to do anything. sudo should not depend on network configurations. It sounds very very dangerous!