Original message at bottom. replies from: Mark Montague <markmont@umich.edu> system administration account <sysadmin@astro.su.se> Allan West <allan@nwe.ufl.edu> Thomas Anders <anders@hmi.de> The resolution was on-the-fly editing of the .sversionrc file to change the user name. Allan West listed additional files: "We edit four files, replacing the user's home dir and userid: $HOME/office52/instdb.ins $HOME/office52/user/sofficerc $HOME/office52/user/config/javarc $HOME/.sversionrc" I will look at those as well to see what the implications are. But, for the moment, editing the one file got things running. ------------ Step-by-step: (1) do the server shared-environment install of Staroffice (2) start up a new session on a SunRay and go through the client install until it works. this actually takes several steps. you do the install. you run it again and it asks you for some first time information. you run it again.... until it runs cleanly. (3) copy all the files that got installed on that SunRay account (e.g. utcu0) to the prototype directory for SunRay kiosk sessions. files/directories included: -rw-r--r-- 1 utcu0 nobody 71 Jun 7 14:30 .sversionrc -rw-r--r-- 1 utcu0 nobody 8192 Jun 7 14:34 .user52.rdb -rw-r--r-- 1 utcu0 nobody 573 May 8 2000 StarOffice52 drwx------ 3 utcu0 nobody 512 Jun 7 14:54 office52 (4) the file .sversionrc contains the user name. if it doesn't match, Staroffice wants to do a client install from scratch again. so I added a piece of script to the prototype profile that does the following: sed "s/utcu0/$LOGNAME/g" /opt/SUNWut/kiosk/prototypes/netscape/.sversionrc \ > $HOME/.sversionrc this grabs the prototype file .sversionrc, replaces the account name utcu0 with the proper account name and sends the resulting file to the current home directory. For those who are unfamiliar with SunRay kiosk mode, logging out a kiosk session scraps the home directory entirely, rebuilds it from scratch using the prototype, and logs the user back in. Therefore, anytime there is a login, it can be assumed that the files have reverted to the prototype and any editing required has to be done again. That's why the line of code is in the profile. (5) this is really a separate step, but the mime types and mailcap entries had to be modified to get any .doc, .xls, etc files downloaded with netscape to automatically launch and open in Staroffice. For kiosk mode, Staroffice also wanted to be added to the desktop menu so that users could select it directly. --------------- Chris Hoogendyk -- O__ ---- Network Specialist & Unix Systems Administrator c/ /'_ --- Library Information Systems & Technology Services (*) \(*) -- W.E.B. Du Bois Library ~~~~~~~~~~ - University of Massachusetts, Amherst <choogend@library.umass.edu> --------------- -------- Original Message -------- Subject: star office52 user install Date: Fri, 07 Jun 2002 16:26:46 -0400 From: Chris Hoogendyk <choogend@library.umass.edu> Reply-To: choogend@library.umass.edu Organization: UMass Library To: Sun Managers <sunmanagers@sunmanagers.org> I have installed Star Office 5.2 as a shared server install, and then end up having to do a user specific install for each user. I have cloned one user's install, and can use it as a prototype to reconstruct that user successfully (this is in kiosk mode on SunRays). In other words, when that SunRay does a logout, it blows away the kiosk mode user account and then rebuilds it automatically from the prototype. For this one user, it works. On other users, even though the prototype is cloned, Star Office sees something that doesn't fit and does a user install the first time you run it. I have gone through the files in the prototype searching for something that tags it to that user and haven't been able to find anything. Does anyone know where Star Office tracks this stuff and how to get it to accept the cloned prototype as a valid installation? --------------- Chris Hoogendyk -- O__ ---- Network Specialist & Unix Systems Administrator c/ /'_ --- Library Information Systems & Technology Services (*) \(*) -- W.E.B. Du Bois Library ~~~~~~~~~~ - University of Massachusetts, Amherst <choogend@library.umass.edu> --------------- _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Mon Jun 10 13:15:07 2002
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:46 EST