I think this bug is marked as "In progress" and Martin Pitt is assigned to it and from reading the comments (have any of you actually read the comments?), he said in comment #1:
"I agree that sudo doesn't need to look up the hostname IF the relevant host part in sudoers is "ALL" anyway." Any comment after that has been pointless, since comment #1 is all this bug is about. If you have any other issue (something breaks your hostname, you don't like sudo's design, etc.), please, open a new bug report or a wiki page or a spec. This is not a discussion forum. This bug is known, this bug is acknowledged, it only remains to give a patch. So if you don't have a patch, you are not helping. On the contrary, you are flooding people's inbox and making them to lose interest in this bug. If you want to help, grab the source code of sudo and figure out how to avoid calling gethostbyname() when /etc/sudoers does not contain any hostname to resolve. As far as I know, sudo is not maintained by Canonical, so bringing the issue to the original developers may also help to solve this bug (perhaps it is already solved in a recent version). http://www.gratisoft.us/sudo/ Thanks. -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://bugs.launchpad.net/bugs/32906 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
