I suspect you have a firewall issue of some sort. Have you tried
completely disabling SELinux?
That's what we're recommending for our next release that supports RHEL5
and SLES10...
-Bob
Philippe Bourdeu d'Aguerre wrote:
Le mardi 4 mars 2008, Bob Doolittle a écrit :
AMGH is not designed to work on private networks. There are cases where
the protocol will attempt to contact the primary interface, and if the
DTUs can't reach it, AMGH will behave unpredictably. One thing you
could try is to set up host routes for the primary interface IPs which
direct to the private interface on the appropriate machine.
I would like to try your first idea:
Le jeudi 28 février 2008, Bob Doolittle a écrit :
If you don't mind an unsupported solution, and you don't mind hacking
some software, you could easily
- write a wrapper for utswitch that chooses a server based on the token
type, and
- instrument /usr/dt/config/Xsetup to run it
But for this, I need to get utswitch working:
Le mardi 4 mars 2008, Philippe Bourdeu d'Aguerre a écrit :
utswitch works from madiran (CentOS) to quercy (Solaris) but from quercy to
madiran, it fails silently and quickly (SunRay switching symbol doesn't
appear). I also tried to switch from a server to itself: it works on both
servers, I see DTU switching symbol, then my session resumes.
Does you know what could make utswitch fails silently ?
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
