I ran into an issue because we applied JDS templates to customize the desktop environment for all users, so since it was set as mandatory at the system level, the kiosk JDS3 gconfdata couldn't write data.
Example errors: Can't overwrite existing read-only value: Value for `/apps/gnome-session/options/logout_effect' set in a read-only source at the front of your configuration path Can't overwrite existing read-only value: Value for `/desktop/gnome/background/picture_options' set in a read-only source at the front of your configuration path I edited the gconf xml files in the jds3/gconfdata directory to remove the XML entities that were already set at the system level, but I had to edit the jds3-kiosk-session executable as well because it does additional gconftool-2 calls (line numbers on the left): 91 *) 92 theMode="none" 93 theColor=$inBackground 94 ;; 95 esac ---to----> 91 *) 92 theMode="" 93 theColor="" 94 ;; 95 esac Of course, specifying background options to JDS will yield the same error because gconftool-2 will run again, but the catch-all in the 'case' block created a problem when even no arguments were provided to the session. Anyhow, is there another / better way to handle the JDS configuration templates? On a separate note, I wish I saw that blog entry before, the fact that we can use the Sun Ray datastore to define alternate kiosk sessions for specific tokens is awesome! Best Regards, Nick Ross -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bob Doolittle Sent: Friday, July 24, 2009 7:40 PM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] JDS Applications via CLI Joerg's blog should provide some guidance: http://blogs.sun.com/joergb/entry/using_different_kiosk_sessions_for What he's trying to do is more complex than you are asking, but he covers the basics well and it should be easy to map to the simple case. -Bob Nick Ross wrote: > Unless I'm mistaken, I think I found it: > > /opt/SUNWut/sbin/utkiosk -I session -A myapplist.txt > > Where 'myapplist.txt' contains a line for each application with the following > fields: > > <desc|exec>: <.conf name or path>: <user|critical|auto>; > > For example, for the default 'calculator.conf' in > /etc/opt/SUNWkio/applications, the utkiok file would read: > > desc:calculator:user; > > Correct? > > Best Regards, > Nick Ross > ========================== > > From: [email protected] > [mailto:[email protected]] On Behalf Of Nick Ross > Sent: Friday, July 24, 2009 7:01 PM > To: SunRay-Users mailing list > Subject: [SunRay-Users] JDS Applications via CLI > > Does anyone know how to specify applications to be used in a JDS kiosk > session via CLI? Assuming the applications are defined in > /etc/opt/SUNWkio/applications, is there a way to set which applications > should be used, and their mode (critical, user, etc.) *without* using the Sun > Ray web administration console? > > Best Regards, > Nick Ross > _______________________________________________ > 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
