[Bug 1342580] Re: tftpd-hpa doesn't start on boot

2015-01-05 Thread falstaff
A workaround for my case was to bind to the IPv4 address explicitly: In /etc/default/tftpd-hpa: TFTP_ADDRESS="0.0.0.0:69" -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in Ubuntu. https://bugs.launchpad.net/bugs/1342580 Tit

[Bug 1342580] Re: tftpd-hpa doesn't start on boot

2015-01-05 Thread falstaff
** Attachment added: "syslog-tftp-hpa-net-device-up.txt" https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1342580/+attachment/4292436/+files/syslog-tftp-hpa-net-device-up.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tf

[Bug 1342580] Re: tftpd-hpa doesn't start on boot

2015-01-05 Thread falstaff
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 so

[Bug 479614] Re: net usershare info takes too long (was: Nautilus hangs from time to time)

2009-11-12 Thread falstaff
I found out what was wrong: I copied the smb.conf from my old setup, where I used KVM and had several vnet's. This line in smb.conf allowed me to share files only with my virtual machines: interfaces = 127.0.0.0/8 vnet0 vnet1 vnet2 I did not setup kvm that way again, therefor I had no vnet0-2

[Bug 479614] Re: net usershare info takes too long (was: Nautilus hangs from time to time)

2009-11-12 Thread falstaff
, but I did not experienced such hangs. I discovered that starting the samba daemon also takes a long time... Bye falstaff ** Attachment added: "nsswitch.conf" http://launchpadlibrarian.net/35576626/nsswitch.conf -- net usershare info takes too long (was: Nautilus hangs from ti

[Bug 479614] Re: net usershare info takes too long (was: Nautilus hangs from time to time)

2009-11-12 Thread falstaff
I asked myself why it has two times the same nameserver in this list. Its because im connected two times to that network, over wireless and ethernet. When I disable one connection, one nameserver disappears. Nevertheless the problem persists... ** Attachment added: "resolv.conf" http://launchpa

[Bug 479614] Re: net usershare info takes too long (was: Nautilus hangs from time to time)

2009-11-12 Thread falstaff
** Attachment added: "hosts" http://launchpadlibrarian.net/35569828/hosts -- net usershare info takes too long (was: Nautilus hangs from time to time) https://bugs.launchpad.net/bugs/479614 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed

[Bug 479614] Re: net usershare info takes too long (was: Nautilus hangs from time to time)

2009-11-12 Thread falstaff
Oops, sorry, that was not intended... Again an strace... $ time strace net usershare info 2> strace-info.txt real1m24.015s user0m0.030s sys 0m0.030s strace-info.txt is attached. It hangs at the same line as "list" does... $ hostname -f alpha hosts and resolv.conf is attached... I do

[Bug 479614] Re: net usershare info takes too long (was: Nautilus hangs from time to time)

2009-11-11 Thread falstaff
Hi, My setup is a typical home setup, no domain server or something like that, local user accounts. I have a D-Link DIR-855 Router at 192.168.220.1 which also acts as DHCP and DNS-Server (DNS-forwarding or something like that). That router has also the ability to share an attached USB-Harddisk (SM