On Fri, Jan 15, 2010 at 7:03 PM, james <[email protected]> wrote: >> What do you think could be happening? There is definitely a >> peer-dependent delay when booting these thing. There must be some >> contention going on during a mass (>1) boot, but I don't know where >> else to look. Any ideas? > > Dave I cannot recall what we did, it was easy to find in the man, but the > servers have DenialOfService delays built in. We increased the number of > simultainious clients I think on DHCP. > Wireshark is easy to use and very helpful to show exactly what is happening. > > James
Sorry to leave this thread so long before coming back to it. It just wasn't the highest priority for a time. tcpdump on the ltsp server show that the client makes an unreplied request to port 2001 on the server. ps shows that inetd is listening on that port, and grep shows that it's the nbd image specifically: 2001 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/i386.img I don't see anything in inetd.conf about denial of service, or max connect attempts. As I mentioned in a previous post in this thread, my /opt/ltsp/images/i386.img lives in RAM and the server is showing a 0 load while this delay is happening. Thanks for looking. db ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
