Hello David,

  It all boils down to files in a home directory.

  When your Kiosk session starts and its temporary user is
  initialized, the template paths are copied to the user's
  newly (re-)created home dir.

  To configure a Mozilla/Firefox session I usually did this:
  started with a Regular user session (or tweaked a kiosk
  session to have a terminal), configured the browser and
  closed it. Put all attention to details like splash screen,
  proxy servers, etc.

  After the browser is closed I restart it to check that
  its configuration files created and saved in my current
  user's home are sufficient for my needs (perhaps I also
  wipe the file cache after the tests), and close it again.

  Now is a good moment to tar the ~/.mozilla or ~/.firefox
  or ~/.opera directory and get its contents to the Kiosk
  template.

  Just in case you'd use FLButselector package to customize
  Kiosks per-user or per-DTU, its browser wrapper-scripts
  can be provided a tarball of user's preferences and unpack
  it before starting the browser. This allows, for example,
  to save a certain user's (person's) proxy password into
  his or her individual tarball.

  We used this trick on one setup where users of a locked-down
  organization did not know their random proxy passwords, so
  they couldn't get to internet from their Windows workplaces,
  but only from a preconfigured terminal session they could...

//Jim
  
Thursday, July 10, 2008, 4:14:42 AM, you wrote:

DK> I'm going to persist with the n00bish questions :)


>> 4) In the SRSS Kiosk admin page, I enter the following arguments to the
>> FF executable:
>>
>> -profile "/var/opt/SUNWkio/home/*/.mozilla/firefox/FFKiosk" -kiosk

DK> This seems to work OK - except that I have discovered that I cannot
DK> run more than one session concurrently on more than one DTU - as the
DK> profile seems to be "fought" over.

DK> Clearly I'm doing this wrong, so dumbing it right down; if I have
DK> configured a Firefox profile with the goodies I want to propagate to all
DK> kiosk users, whereabouts and what file name do I give it to achieve
DK> this?

DK> Eg. assuming my template is:
DK> /etc/optSUNWkio/prototypes/jds3/.mozilla/firefox/FFKiosk

DK> How do I get the kiosk user session to pick it up and use it? The kiosk
DK> session always wants to use
DK> /var/opt/SUNWKio/home/ut*/.mozilla/firefox/12345678.default
DK> as the profile.

DK> Cheers!
DK> Dave



>>      Similar to above   you need to put  a  prepared
>> .mozilla/firefox   directory ( template )
>> in  /etc/opt/SUNWkio/prototypes/jds3  complete  with all  the
>> extensions  and Plugins
>> you want the kiosk user to have.>
>>
>> The reason your additional  stuff  dont show up is because the kiosk
>> user has a virgin  .mozilla/firefox
>> directory everytime the kiosk is regenerated.

DK> //Lars


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



-- 
Best regards,
 Jim Klimov                            mailto:[EMAIL PROTECTED]

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

Reply via email to