[Bug 310250] Re: ltsp-client: attempted to send on closed socket

Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as "Won't Fix". ** Changed in: ltsp (Ubuntu Hardy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subsc

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the report. The bug has been fixed in newer releases of Ubuntu. ** Changed in: ltsp (Ubuntu Intrepid) Status: Confirmed => Invalid -- ltsp-client: attempted to send on closed socket https://bugs.launchpad.net/bugs/310250

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

OK. Thank you very much! -- ltsp-client: attempted to send on closed socket https://bugs.launchpad.net/bugs/310250 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.ub

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

nominated and confirmed for hardy ** Changed in: ltsp (Ubuntu Hardy) Status: New => Confirmed -- ltsp-client: attempted to send on closed socket https://bugs.launchpad.net/bugs/310250 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

nominated and confirmed for intrepid (if someone finds the time for an SRU) ** Changed in: ltsp (Ubuntu Intrepid) Status: New => Confirmed -- ltsp-client: attempted to send on closed socket https://bugs.launchpad.net/bugs/310250 You received this bug notification because you are a member

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

** Changed in: ltsp (Ubuntu) Status: New => Confirmed ** Changed in: ltsp (Ubuntu) Assignee: (unassigned) => Rubeosis (faspie) -- ltsp-client: attempted to send on closed socket https://bugs.launchpad.net/bugs/310250 You received this bug notification because you are a member of Ubun

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

Sorry, I did not remember that I reported the bug as nbd-bug. Could you please move it to the ltsp section. I don't know how to do that... -- ltsp-client: attempted to send on closed socket https://bugs.launchpad.net/bugs/310250 You received this bug notification because you are a member of Ubunt

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

this was fixed in ltsp-5.1.25 (upstram commit 879 http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/879) ** Changed in: ltsp (Ubuntu) Assignee: Rubeosis (faspie) => (unassigned) Status: Confirmed => Fix Released -- ltsp-client: attempted to send on closed socket htt

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

this is an ltsp specific prob, marking invalid for nbd ** Changed in: nbd Status: New => Invalid -- ltsp-client: attempted to send on closed socket https://bugs.launchpad.net/bugs/310250 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubu

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

I would suggest adding the -persist parameter to the initrd. However, I don't have any idea how to do that... There are two rc-scripts left: /etc/init.d/nbd-client /etc/init.d/ltsp-client-setup I would suggest to add the -persist option here, too. -- ltsp-client: attempted to send on closed so

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

This seems to be the same problem. http://www.mail-archive.com/ltsp- disc...@lists.sourceforge.net/msg35112.html Solution (see there): " > Hello, > > because of importance of these probĺems we have now 3 ways to protect > the clients from freeze because of loosing connections: > > 1. TCP-Keep

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

"why are you using xinetd ?" -- no idea, I just setup a new server, installed ltsp-server-standalone, followed by ltsp-build-client -- then it complained that I'm using xinetd instead of inetd. Indeed, no client was able to download i386.img at boot time. So I typed "apt-get install openbsd-inetd

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

** Also affects: nbd Importance: Undecided Status: New -- ltsp-client: attempted to send on closed socket https://bugs.launchpad.net/bugs/310250 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubunt

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

I cannot believe that this is a problem of xinetd. I converted the inet.conf via xconv.pl, it should do exactly what inetd does. Please refer also to similar bugs and bugfixes, e. g. http://lwn.net/Articles/267685/. I think, it is a fundamental problem of nbdrootd. Are you able to reboot the ser

[Bug 310250] Re: ltsp-client: attempted to send on closed socket

why are you using xinetd ? by default ltsp-server depends on openbsd- inetd since this is the only inetd tested and shipped in ubuntu ltsp installations, i would assume something in your xinetd setup is missing, please refer to the xientd documentation. ** Changed in: ltsp (Ubuntu) Status: