Yes, the exec is calling the jds3v2-kiosk-session (I only changed the name for
logging purposes.) and the sub-directories/files within sessions/jds3v2 exist.
However, the .../prototypes/jds3v2 directory is comprised of the altered files
so the panels are different than those within .../prototypes/jds3.
Thanks for the tip on the debug, hopefully there is something in that article
that I have missed when I previously enabled debug; I'll post anything that
seems strange.
Given that the jds3 and jds3v2 kiosk versions work as anticipated if I set
either/or as the default I suspect I have something wrong within meta-kiosk or
I'm trying to make meta-kiosk do something it wasn't intended. I've not seen
any articles about people trying to do what I'm doing, just those using it to
change between JDS, UTTSC, etc.
____
You mean the exec is set to jd3v2-kiosk-session?
In order for this to work, the following the following needs to exist:
/etc/opt/SUWNkio/sessions/jds3v2/jds3v2-kiosk-session
/etc/opt/SUWNkio/sessions/jds3v2/applauncher
/etc/opt/SUNWkio/prototypes/jds3v2/(contents exactly the same as jds3
prototypes0
Kiosk is very well logged if your turn on debug and change set Sun Ray messages
to user.debug priority (you can skip the pam.conf change if you want, but it is
very insightful to watch a kiosk session get built) See:
http://wikis.sun.com/display/DVDEV/Logging+Levels
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
