Comment 59 for bug 32906
Revision history for this message
| Martin Pitt (pitti) wrote Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on | #59 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Aah, I finally found out why I could not reproduce it, and what's wrong. I have local MTAs on all my boxes. If I install a system without one, I can replicate the error. It apparently tries to send a mail to the admin about the error and dies with a SIGPIPE:
Program received signal SIGPIPE, Broken pipe.
0x00007fcef7181bb0 in write () from /lib/libc.so.6
(gdb) bt
#0 0x00007fcef7181bb0 in write () from /lib/libc.so.6
#1 0x00007fcef7125ce3 in _IO_file_write () from /lib/libc.so.6
#2 0x00007fcef7125bc4 in _IO_do_write () from /lib/libc.so.6
#3 0x00007fcef7126e20 in _IO_file_close_it () from /lib/libc.so.6
#4 0x00007fcef711adfa in fclose () from /lib/libc.so.6
#5 0x0000000000405d36 in send_mail (line=0x62fe60 "unable to resolve host foo") at ../logging.c:564
#6 0x0000000000406637 in log_error (flags=9, fmt=0x411d08 "unable to resolve host %s") at ../logging.c:432
#7 0x0000000000407cf8 in set_fqdn () at ../sudo.c:1160
#8 0x0000000000408c4d in main (argc=<value optimized out>, argv=<value optimized out>, envp=0x7fffffa4
at ../sudo.c:608
This looks suspiciously similar to bug 193516.
I'll take a stab at this now.