Rats - looks like an errata is in order. The engineer quoted
below follows up with this mail:
Actually, I didn't read this carefully enough. What turns off the group
manager is enableGroupManager=false. enableLoadBalancing=false stops
load balancing completely, so Sun Rays stay on the server to which they
first connect. There is no propagation of it across servers.
So I think I described it to you properly, and utadm -f is still
preferable, but it's not so bad as to recommend deprecation
after all.
-Bob
Bob Doolittle wrote:
Wolfgang Engelien wrote:
I got a chooser for the servers on a new login immediately after the
changes were made. (I did not use "utadm -f").
Chooser yes, load balancing change, no.
Again I encourage you to use utadm -f instead.
That will also take immediate effect.
This morning, after speaking to the engineer who is
the author/expert of this area, he responded with the
following:
enableLoadBalancing=false essentially shuts off the group manager
completely. You don't want to do that. It was mainly there as a way of
backing out the feature early on in case of bugs.
I'm recommending we remove this option from auth.props
in a future release since it should be deprecated and seems
to have less utility than utadm -f.
-Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
