On Dec 18, 2007 5:22 PM, LeBar, Russell J <[EMAIL PROTECTED]> wrote: > > > Would it be enough to change the /etc/opt/SUNWut/jre symbolic link? > > > > Yes. That would change the JRE being used by all of the Java > > components in SRSS. If you want to just change the JRE being > > used by the SRSS Java GUI apps then you can create a > > /etc/opt/SUNWut/guijre symlink. If that symlink exists then > > the GUI apps (utsettings, utmhconfig, the self-registration > > dialogues) use it, otherwise they use the SUNWut/jre symlink. > > Ahh, so that's what that check is for. I saw references to guijre even though > we > do not have a symlink with that name. I'm fine with switching everything to > Java 6 though (or if I have to, go back to Java 5).
Any Java since 1.4.2 should work for SRSS 3.1. > So all I need to do is change the symlink. Should I do a utrestart? Or a > utrestart -c? Or stop utsvc and utds via init.d? I'd change the symlink, verify that the new one works (run '/etc/opt/SUNWut/jre/bin/java -version' and verify that it's a 32-bit JRE of a suitable version) and then do a 'utrestart'. Don't try to run the init.d scripts manually, they have non-obvious dependencies and you could end up with a half-working system. > [...] So based on comments below it sounds like the auth manager is the > only real concern. If authd breaks then all of SRSS will fail. > > If SRSS is generally behaving properly > > then the SRSS auth daemon (a non-GUI Java app) must be happy > > with the current JRE. > > Now you have me a bit concerned. If it uses the /etc/opt/SUNWut/jre > symbolic link then that no longer exists. I haven't stop/started the SRSS > so it could just be running off of an image already loaded into RAM that > no longer exists on disk. Sounds like it's living on the ghost of its original JRE. I didn't realise that the original JRE had been yanked from underneath a running authd. It's kinda cool that it's still running but it's pretty scary too. > What causes the auth manager to restart? Does a utrestart -c do it? Any 'utrestart' will do it. A 'utrestart -c' will stop it and keep it down for long enough that existing sessions will give up and die. A simple 'utrestart' will stop it and then start a new one immediately, allowing existing sessions to continue to run. > Thanks for the help on this. I am thinking that I should fix > /etc/opt/SUNWut/jre and then cycle the SRSS just to be safe. Yes. Better to do that at a time of your choosing than to have authd drop dead unexpectedly if it goes looking for some JRE file that no longer exists -- or perhaps, if you've remade the symlink but not started a fresh authd, finding a file that belongs to a different JRE. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
