On Mon, Feb 13, 2012 at 08:49:10AM -0000, Alkis Georgopoulos wrote: > Another idea to work around the problem: > Wouldn't it be possible to somehow specify that we only want one > nbd-server process for all the clients?
Well, one of my long-term goals is to convert nbd-server from fork-per-process to a select() or better paradigm. Just hasn't happened yet. Once that's set up, there would be only one process for all the clients. However, I don't see how this would be a workaround for the problem described in this bug? > I've heard of LTSP installations with thousand of clients, so even if one > nbd-server process only needs as little as 1 Mb RAM, that would still amount > to some Gb for thousands of clients. Not really, since many of the pages will be shared; only the per-client state wouldn't be. > The "user" option of nbd-server would need to be per-process, not per export then. Actually, the user option of nbd-server is a global option, not a per-export one. > I haven't seen the code of nbd-server at all, I don't know if it uses > "select" or "fork" to serve multiple clients, so I don't know how easily > that could be accomplished. The latter. -- The volume of a pizza of thickness a and radius z can be described by the following formula: pi zz a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696454 Title: NBD booted clients don't close the connection on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/696454/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
