The kiosks are generally a mix of web browsers (in various configurations) and SSH sessions running in gnome-terminal. They also need to print, and so far (on the old terminal server running LTSP), I've just used the AllowedUsers directive in CUPS to limit printers to specific users (some users have 1 printer, some have a handful). I'm not sure that would work with kiosk mode since the username changes at every login.
-Jon ----- Original Message ----- From: "Craig Bender" <[email protected]> To: [email protected] Sent: Tuesday, November 2, 2010 2:40:48 PM Subject: Re: [SunRay-Users] GDM Auto Login I haven't done what you are trying to do, but I do think Kiosk is the way to go (plus it's supported). You can specify certain tokens (whether pseudo or smart card) to run kiosk mode. This is done by registering the token, then using the web gui to set that token to either kiosk or regular (or you can use utkioskoverride). From there, the question I'd ask is what do you want the various kiosks to do? A simple if/then script based on token ID could launch different programs. If more complex, you could create specific kiosk sessions types and using utkioskoverride assign them to the tokens. On 11/2/10 12:18 PM, Jonathan C. Bailey wrote: > Hello, > > I don't think this is Sun Ray specific, but here goes... I have a Oracle > Enterprise Linux 5u5 server with Sun Ray Software 5.1 installed. I'm trying > to get a timed login working for specific DTUs that are acting as kiosks. > Kiosk included with SRS won't do what I want since each kiosk is a fairly > unique setup (much easier to manage as normal users). Anyway, I've configured > the lines in /etc/gdm/custon.conf (omitting some extra junk): > > [daemon] > TimedLoginEnable=true > TimedLogin=/usr/local/bin/gdm_autologin.sh| > > [security] > AllowRemoteAutoLogin=true > > And the following script (/usr/local/bin/gdm_autologin.sh): > #! /bin/sh > > LOGFILE="/var/log/gdm_autologin.log" > TS=`date +%c` > > exec 2>&- > > trim() { echo $1; } > > DISP=`echo $DISPLAY | cut -d\: -f2 | cut -d. -f1` > TOKEN=`cat /var/opt/SUNWut/displays/$DISP | grep TOKEN | grep -v INSERT_TOKEN > | grep -v TOKEN_SET | cut -d\= -f2 | cut -d. -f2` > OTHERINFO=$(trim `/opt/SUNWut/sbin/utdesktop -p $TOKEN | grep "Other Info" | > cut -d\= -f2`) > UNAME="BORK" > > if [ "${OTHERINFO:0:10}" == "autologin:" ] > then > export UNAME > UNAME=`echo $OTHERINFO | cut -d\: -f2` > fi > > echo $UNAME > > echo "[$TS] UNAME=$UNAME DISPLAY=$DISP TOKEN=$TOKEN OTHERINFO=$OTHERINFO">> > $LOGFILE > > exit 0 > > --------------------------------------------------------- > With this setup, I SHOULD be able to set the "other info" field for a DTU to > "autologin:USERNAME" and have it work, but all I get is the timed login count > down without a username listed. I've tested the script from the command line > and it returns a username. Also, from the log the script creates, it's > running, and the UNAME variable is being populated. Has anyone else done > something similar, or have an idea why it isn't working? > > [Mon 01 Nov 2010 05:59:44 PM CDT] UNAME=trskiosk2 DISPLAY=11 > TOKEN=c2f6c84bad22dfdcb8eae14eb617aeef OTHERINFO=autologin:trskiosk2 > > > > -Jon > _______________________________________________ > 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
