Joerg Barfurth wrote:
Gérard Henry schrieb:
hello all,
i'd like to talk again about this very interesting old post:
http://www.mail-archive.com/[email protected]/msg03031.html

my config is:
V440 Sol10 SRSS 3.1
V210 Sol10 SRSS 3.1
and we don't use smart cards, so when a DTU displays v210's login screen, it never change even if load on V210 is higher than v440! The only workaround i found so far is to do "utrestart -c" on v210 to force DTU to display v440's login screen.

i don't understand what does bob mean when he says:
"Non-Smartcard sessions are a little surprising,
because they only load-balance after the username
is entered...."
Does it mean that the scenario is:
- DTU is displaying servA login screen
- user enters his name and passwd
- user is logged into servB because servA has less free ressources than servB? As i've never noticed a such behavior... or perhaps, am i missing something?


That load-balancing step only happens, if you have NSCM enabled. With NSCM enabled there will indeed be loadbalancing after the user name was entered and before the rest of the authentication takes place.

Right. If you look in /etc/pam.conf, you can see that with NSCM we use two separate PAM services for the username (utgulogin) and the reset of the authentication (utnsclogin). That's because these happen in separate processes, potentially on separate servers. We sometimes call this "lazy authentication", because like the common technique of "lazy loading" (http://en.wikipedia.org/wiki/Lazy_loading) we put off authentication as late as possible so that we can potentially load-balance after the username is known.

If you are not using NSCM and are at the native Solaris login screen, then no further load balancing will take place - iirc even when you log in and back out.

No, that's incorrect. In /usr/dt/config/Xreset we do a "utswitch -t", which will load balance after logout so the next greeter can be on a different server (this is for all forms of sessions).

In the latter case in order to get a session rebalanced you need to kill the Sun Ray session. Using utsession -k or terminating the session from the web UI will do this. But (afaik) there is no way for the user to get the session rebalanced - logged in or not.

Sorry - this is wrong. If you log out and in again, you will potentially be load balanced to a different server. Always.

-Bob


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

Reply via email to