----- Original Message ----- From: Joerg Barfurth <[EMAIL PROTECTED]> Date: Tuesday, October 7, 2008 2:03 am Subject: Re: [SunRay-Users] Timeout Values To: [EMAIL PROTECTED], SunRay-Users mailing list <[email protected]> Cc: "P.S.M. Swamiji" <[EMAIL PROTECTED]>
> Troy Knabe schrieb: > > >>> For the Kiosk mode I see two different places for timeout > >>> settings. I have copied them in below. My issue is that I am > >>> seeing a lot of Login Greeter/Idle Sessions and I think the first > >>> "Timeout" setting should be set lower, but I don't want to > >>> disconnect good sessions. > >>> > > If you see sessions that are marked as 'Login Greeter/Idle' in > the Sun > Ray management web console (or in utsession(1M)), then these are > not > valid kiosk sessions. A kiosk session should remain in this > state only > for a very short time. Sessions that are marked as 'Idle' should > show a > Unix login greeter. > > If these session should be kiosk sessions and show only a black > screen, > then something in kiosk session setup is failing. You should > check the > system messages log for 'error' messages from Kiosk Mode. Yes, I am seeing this, and have googled to no avail. Any suggestions?? kioskcrit[18355]: [ID 702911 user.error] Error: critical application (pid=18357) exited with non zero status Oct 7 07:27:22 server kioskcrit[18355]: [ID 702911 user.error] Error: critical application (pid=18357) exited with non zero status Oct 7 07:27:23 server kiosk:uttsc[26165]: [ID 702911 user.error] /opt/SUNWuttsc/bin/uttsc exited with error code 17 - exiting Oct 7 07:27:23 server kiosk:uttsc[26165]: [ID 702911 user.error] /opt/SUNWuttsc/bin/uttsc exited with error code 17 - exiting > > A 'Idle' session in that sense will be terminated automatically > if it > remains disconnected for a certain duration. That timeout is not > configurable. > > >>> One here in the admin gui under "Advanced" and "kiosk mode" > >>> > >>> Session: > >>> > >>> Sun Ray Connector for Windows OS > >>> > >>> Timeout: > >>> > >>> 24000 seconds > >> > >> This is for the timeout the session needs to be keep on disconeect. > >> After timeout reached the disconnected session will be > killed.> > > > > I don't quite understand this, can you explain this in some more > > detail? > > > > > This timeout generally determines how long a kiosk session - in > your > case the "Sun Ray Connector for Windows OS" kiosk session - will > stay > 'alive' in a disconnected state. > > If the session has remained disconnected for the given time, it > will be > terminated. If the session is connected to again before the > timeout has > elapsed, nothing happens. A timeout of 0 indicates that the > session is > terminated immediately when disconnected. An empty value is used > to > request that the session is never terminated due to being > disconnected. > The Sun Ray management web console and various command line > tools will > indicate sessions that are considered disconnected. Sessions > become > disconnected when a card is pulled or inserted in the DTU, when > the DTU > is powered off or when the network to the server is interrupted. > > >> It should not effect connected sessions. > >> > > >>> Under that is a place for "Arguments" > >>> where I see: > >>> > >>> -t 3600 > >>> > >> This is to avoid two minute timeout imposed by WTS. > >> See the /etc/opt/SUNWkio/sessions/uttsc/README for > >> more detailed info on this. > > > > So if I understand this correctly using -t 3600 the behavior I > could > > expect is that every 2 minutes the Windows TS disconnects the > > connection, but every 60 minutes (3600 secs) the entire > session dies and > > is restarted. Correct? > > > > Yes. Note that this only applies to sessions to which a DTU is > connected > and that show the Windows login screen. These sessions > are not > considered 'Idle' by Sun Ray software. > > The two minute timeout of the RDP session for an unused login > screen is > imposed by the Windows TS. AFAIK it is not possible to change or > disable > this timeout on the WTS side. > > To avoid frequent, visually irritating session restarts, the > "Sun Ray > Connector for Windows OS" kiosk session will continuously > restart the > Sun Ray Windows Connector when this happens. After the -t > timeout has > elapsed, the kiosk session will exit and is restarted in order > to allow > configuration changes to be picked up and to allow Sun Ray load > balancing to occur. > > The kiosk session will not try to restart the SRWC, if it > detects that > the session has become disconnected when the Windows Connector > exits > (for example after the 2 minute timeout). In that case it will > exit (and > won't be restarted) independent of any timeout parameters. > > HTH > > - Jörg >
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
