Art, I've run into this kind of thing before, and this is non trivial to check for.
a quick google found these.. http://www.unix.com/solaris/38577-how-monitor-ports.html http://www.cyberciti.biz/tips/linux-scanning-network-for-open-ports.html if you go this scripting route the following things come immediately to mind .. a) allow for server load, maybe it's just slow to answer b) don't put the logic in the kiosk script, that feels like overkill (i.e. running it for *every* WTS login request). might try running it as a cron job (e.g. every X minutes) that removes or comments out the WTS name/IP from the list of acceptable hosts. this could be done on a single server the results shared across NFS. c) make the script notify an admin there's a problem (e.g. send mail, SMS, etc.) hope this helps.. Curtis. On Wed, Apr 13, 2011 at 7:19 PM, Art Peck <arthurp...@aol.com> wrote: > Anyone have a clever way to check that the WTS is ready to accept RDP > connections before launching uttsc? I had a down WTS server yesterday and > since my script doesn't check for that, I had a whole mess of DTUs at 26D > and cycling endlessly. I'd like to not have that again. > > I have thought of a simple ping, but that only says the network stack is > responding, which is something of course, but doesn't tell me that the RDP > stack is ready. > > Thanks! > > Art > -- Curtis Cunningham web: c <http://curtiscunningham.com>urtiscunningham.com
_______________________________________________ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
