Thanks. We will consider chooser type stuff if it starts to be trouble in the field. Would be optional at most. Problem with that is it would add another step to the login for the 95% case where user just wants to get to their one and only desktop. Another approach might be to stop retrying after some number of attempts to re-open uttsc, just to get kicked out 2 minutes later -- end user would need to card out, then card in again to get their desktop. Or even better maybe, put the chooser style dialog in the loop, so the user would be told Windows session was suspended "Click [OK] to restart". None of this is quick and simple of course ...
> ... Ugly older example here Yes, familiar with that. Of course, it would be great if the users would just log into their Windows sessions in the first place. But in our application it is actually not necessary always, so sometimes they do not. "Users will be users." -- Peter Craig Bender <[email protected]> Sent by: [email protected] 16/11/2009 20:56 Please respond to SunRay-Users mailing list To: SunRay-Users mailing list <[email protected]> cc: [email protected] Subject: Re: [SunRay-Users] Annoying Connector proxy logs (repost, with subject this time) I'm pretty sure you cannot bypass the proxy. But you can put a Click Here To Start Windows Box which would solve this and free up resources Ugly older example here: http://blogs.sun.com/ThinkThin/entry/cam_chooser_application You can get really elaborate using tcl/tk. [email protected] wrote: > > Hi Craig, > > > One thing that will help immensely will be to put a loop in the script. > > Actually, we do have a loop in the script, with 5 second sleep after > uttsc exits, if uttsc exits 0. Actually, that why the annoying log > repeats every 2 minutes, for every card in the system not actually > logged into Windows. > > Script snippit: > ---------------- > while [ `sessionConnected` == "true" ] && [ -z `wtsProcessId` ] ; do > > # No Windows connector (uttsc) process for this user exists. > Call the connector. > /opt/SUNWuttsc/bin/uttsc $UTTSCPARMS $WINTERM_SERV_IP > retVal=$? > > # If uttsc exited with error (could not create session for this > User, was killed / failed) exit without re-try > if [ $retVal -ne 0 ] ; then > break; > fi > > # Otherwise sleep briefly to allow for kiosk cleanup, then try > to re-open session (next try will fail if the User is now invalid). > sleep $RESTARTTIMER > > done > ---------------- > > Look about right?? > > Is there some way to turn off the proxy aspect in Solaris trusted > extensions? > > -- peter > > > > > *Craig Bender <[email protected]>* > Sent by: [email protected] > > 16/11/2009 20:27 > Please respond to SunRay-Users mailing list > > > To: SunRay-Users mailing list <[email protected]> > cc: > Subject: Re: [SunRay-Users] Annoying Connector proxy logs > (repost, with subject this time) > > > > > One thing that will help immensely will be to put a loop in the script. > Look at the Sun Ray Windows Connector Kiosk script for an example. > > As far as Linux, we may not use the "proxy" as that was devised for > Solaris with Trusted Extensions. Not sure though (but I can check). > > [email protected] wrote: > > > > [ Darn, previous post forgot the subject line. Please ignore previous > > and respond to this one instead. Stupid fingers! Sorry about that... ] > > > > Hi list, > > We are getting a very annoying logs flood in SRSS logs, using SRS-5 GA > > (SRSS 4.1 + SRWC 2.2), Solaris 10 u6, WTS running on Windows 2003 > > server. Logs are of the form: > > > > Sun Ray Connector proxy:[2370]: [ID 855542 user.error] Child closed > > socket prematurely, session shutdown > > Sun Ray Connector proxy:[3266]: [ID 855542 user.error] Child closed > > socket prematurely, session shutdown > > Sun Ray Connector proxy:[3418]: [ID 855542 user.error] Child closed > > socket prematurely, session shutdown > > Sun Ray Connector proxy:[3534]: [ID 855542 user.error] Child closed > > socket prematurely, session shutdown > > etc, etc, etc forever > > > > I believe these are being generated when user cards are left in the > > DTUs, but Windows kiosk session (through uttsc) has not actually been > > logged into, ie user is sitting in Windows login screen. Every 2 > > minutes, Windows Terminal Services kicks out the windows RDP session if > > it is not yet logged in, and we restart a few seconds later. > > > > Oddly, we do not seem to see these in RHEL 5.2 setup, nominally > > identical otherwise. (We are however seeing some other odd logs I do > > not yet have a good reproduction scenario for ... that's a different > > story.) > > > > Is our understanding correct -- logs triggered as a result of WTS > > killing the RDP session? Could it be a sign of some other config issue > > or something? > > > > Is there some way to suppress these logs?! There are potentially very > > many, darned annoying, and are pointless for our purposes. > > > > Cheers, > > Peter Blatherwick > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > SunRay-Users mailing list > > [email protected] > > http://www.filibeto.org/mailman/listinfo/sunray-users > _______________________________________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/mailman/listinfo/sunray-users > > > ------------------------------------------------------------------------ > > _______________________________________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/mailman/listinfo/sunray-users _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
