Re: [Bug 479614] Re: net usershare info takes too long
On Thursday 12,November,2009 10:56 PM, falstaff wrote: > 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. > Whireshark showed me that the net command (and I suppose the samba > daemon did the same) did DNS requests asking for the IP of this non > existent devices (IN A requests for vnet0, vnet1 and vnet2, is this a > volitional behaviour?). I removed those non existent devices and the bug > is gone now. But anyway, shouldnt call nautilus-share such programms > asynchronious then? > > Sorry, and thanks for your work! > Yes, I suppose it should, but 'net usershare info' should *really* finish fast. I mean, there really isn't any reason 'net usershare info' should be looking anywhere but the usershares directory, which is local. Even if vnet[0-2] existed and could be resolved, 'net usershare info' does not use that information in any way unless I'm mistaken. -- Kind regards, Chow Loong Jin (GPG: 0x8F02A411) Ubuntu Contributing Developer -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 479614] Re: net usershare info takes too long
On Thursday 12,November,2009 04:19 PM, Thierry Carrez wrote: > Yes, like I said in comment 9, net usershare list is very local, so it > shouldn't really need to resolve names. I suspect some TCP connections > against the local system hostname that would trigger a simple resolution > (that may fail on faulty setups). If that doesn't prove right, next step > is looking in the code itself to understand :) > That's net usershare list. What I'm asking is if net usershare info is any different? Anyway, if resolving the local system hostname is what's causing issues, then perhaps it's a faulty /etc/hosts? falstaff, could you attach your /etc/hosts and the output of "hostname -f"? -- Kind regards, Chow Loong Jin (GPG: 0x8F02A411) Ubuntu Contributing Developer -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 479614] Re: net usershare info takes too long
On Thursday 12,November,2009 03:57 PM, Thierry Carrez wrote: > The trace also seems to point to an issue in your name resolution > configuration. Either failing to connect to 192.168.220.1 for name > resolution, or failing to get an answer from it... > What happens if you run "ping $(hostname)" ? Could you attach your > /etc/resolv.conf and /etc/hosts ? > Out of curiosity, why does 'net usershare info' need to resolve a hostname? What hostname would this be anyway? -- Kind regards, Chow Loong Jin (GPG: 0x8F02A411) Ubuntu Contributing Developer -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs