sunray session working in containers
Hi!
I have search in several forums but It's not clear for me if ti's possilbe have sunray sessions in zones containers.
Release Notes says that SRSS only works on global zones, but I read an article that recommends "run" sunray sessions on differents containers. If an application from a user uses a lot of resources, it will be in their own space and will not affect all the server.
In fact we have detect problems with Browser. When the user access an specific Web Page the CPU reachs 100% of utilization and the server gets very slow.
Could someone explain me if using zones it's the solution or maybe I'm misunderstanding and what I have to use is only Solaris Resource Manager to assign specific resources to Sun Ray users.
Thanks in advance for your help
[802 byte] By [
acpa] at [2007-11-26 15:34:30]
# 1
SRSS can not run in a local zone. SRSS depends on being able to execute with a particular set of privileges, and some of those privileges are ones that are not allowed within a local zone.
In principle you could run SRSS itself in the global zone and arrange to have some portion of the user desktop (say, specific applications) run in a local zone. However, if you do that the application is effectively running remotely and it will not have access to features like audio. Using resource caps, or even just nice'ing the browser process and/or allowing it to run only on a specific CPU ('man pbind') is much easier and will probably produce better results.
In the particular case of a process that burns a lot of CPU I don't think Zones will help anyway, at least not until per-zone resource caps are extended to allow per-zone control of CPU usage. Or maybe that's already available, I don't stay on top of those announcements.
OttoM.
__
# 2
Thanks Otto,
I'm going to study about resource caps. In fact I'm going to post a new question because finally we detect the exact process which uses all the resources.
We are trying to understand why, for now we are killing it or turn off when the server hangs.
First we think that running client session was the solution, thanks again for your help
acpa at 2007-7-8 21:51:51 >
