The proposed fix (from #1 as well as the corrected version from #5) does not solve the problem for me. Actually, when I look at what time the system tries to start the tftp-hpa process, it makes it even worse: The process gets started earlier (around ~11s vs ~13s)! Also, the relevant errors look somewhat different (IPv6 resolve error). Fwiw, I use /etc/network/interface to configure eth1 statically.
Default start script ... Jan 5 14:38:30 testseat2 in.tftpd[1052]: cannot resolve local IPv6 bind address: ::(Name or service not known) Jan 5 14:38:30 testseat2 kernel: [ 13.111093] init: tftpd-hpa main process (1052) terminated with status 66 Jan 5 14:38:30 testseat2 kernel: [ 13.111102] init: tftpd-hpa main process ended, respawning ... Altered start script: .... Jan 5 14:30:59 testseat2 kernel: [ 11.365352] init: tftpd-hpa main process (708) terminated with status 66 Jan 5 14:30:59 testseat2 kernel: [ 11.365360] init: tftpd-hpa main process ended, respawning ... ** Attachment added: "syslog-tftp-hpa-default.txt" https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1342580/+attachment/4292435/+files/syslog-tftp-hpa-default.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342580 Title: tftpd-hpa doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1342580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
