Am Mittwoch, den 08.03.2006, 14:12 -0500 schrieb Joe Auerbach: > hmm . . . a five second test shows you to be most right. i was thinking > of internal stuff (my recent adventures in squid confused me). ping > should work fine. Though I stand by my netstat from the server and note > that you could refine it. netstat. grep out ltsp. make sure that each > ws (or however you define them) only displays once and that should do > it. there's probably an easier way to do it, but that's off the top of > my head.
"sort -u" might be your friend there, in combination with a bit of "sed". I don't have a LTSP server right at my fingertips, but if you look for any connections to foreign port 6000, that should capture any connections to X displays (corrections welcome). I though along the lines of netstat -np | grep -e "^tcp\ *[0-9]*\ *[0-9]*\ *[0-9\.\:]*\ *[0-9 \.]*:6000\ *" | sed -r "s/^[^:]*:[0-9]*\ *(([0-9\.]*)):6000.*/\\1" | sort -u which is right out of my head, without any sanity checking. Hope to give you an idea Anselm ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _____________________________________________________________________ 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
