Luke Bigum schrieb:
Hi all,

I'm having problems getting multiple kiosk session configurations working. My default session uses 'uttsc' and works fine. I'm trying to create a second, 'browser only' session descriptor but the kiosk session is not being created properly. It appears to be generating a blank session configuration file without the necessary options, rather than sourcing what I've written. I'm using SRSS 4.1 on Centos 5.2.


The broken session descriptor is 'browser':

[r...@sunserver6:~]# utkiosk -l
browser
session


It's configuration, copied from the working 'session' configuration. I've tried putting in KIOSK_SESSION_EXEC, same result:


[r...@sunserver6:~]# utkiosk -e browser
KIOSK_SESSION=browser
KIOSK_SESSION_TIMEOUT_DETACHED=12000
KIOSK_ENABLED=yes


The session descriptor file, for the moment executing the same perl script my default kiosk session does (so I know it works):

[r...@sunserver6:~]# cat /etc/opt/SUNWkio/sessions/browser.conf
KIOSK_SESSION_EXEC=/usr/local/sbin/sunserver-balancer.pl
KIOSK_SESSION_LABEL="iseek Sun Ray Connector for Browser only sessions"


This looks all fine.

I've changed one Token to use the configuration name 'browser' with utkioskoverride. When trying to launch this Token's session, you see this error in /var/log/messages:


Jan 28 08:32:48 sunserver6 gdm[14846]: pam_kiosk: pam_sm_authenticate: Initiating Kiosk session with user utku7

Jan 28 08:32:50 sunserver6 kiosk:initsession[14987]: Error: $KIOSK_SESSION not specified

Jan 28 08:32:50 sunserver6 kiosk:initsession[14988]: Error: failed to load Session Descriptor

Jan 28 08:32:50 sunserver6 gdm[14846]: pam_kiosk: pam_sm_setcred: Child process /opt/SUNWkio/lib/initsession failed with exit code 1.


By hacking in some syslog calls, I've traced this error message through SUNWkio's 'initsession' and 'util.sh' scripts, it comes from trying to read what looks like a run time generated session configuration file for the kiosk user, but it doesn't have any necessary content let alone KIOSK_SESSION:


[r...@sunserver6:~]# cat /var/run/opt/SUNWkio/sessions/utku7/session.conf
KIOSK_ENABLED=yes


I've deleted everything under /var/run/opt/SUNWkio/sessions/{user} to start fresh, same problem.


How/why does this temporary session configuration file get generated and why is not a copy of /etc/opt/SUNWkio/sessions/browser.conf as you'd expect? Can anyone spot something wrong with my configuration?


The configuration looks sane.

Please check the output of
    utkiosk -e browser -s
and the content of
   /var/opt/SUNWut/kiosk/:<display-num>/config/srdsConfig
and
   /var/opt/SUNWkio/config/:<display-num>

Where <display-num> is the display number of the kiosk session.

These are intermediate storage places for the kiosk configuration on its way from SRDS to the /var/run/opt file you found.

Where to look next depends on where the data gets lost.

- Jörg

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to