Good to know..... After hunting over this email list I came across
something I think fixed the issue (so far anyway)....
1.
Become superuser on the Sun Ray server.
2.
Change the default DBus resource limits by creating a
/etc/dbus-1/system-local.conf file with the following lines:
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus
Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>
<busconfig>
<!-- default for this is 2048 -->
<limit name="max_completed_connections">32768</limit>
<!-- default for this is 256 -->
<limit name="max_connections_per_user">4096</limit>
</busconfig>
3.
Change the system GDM daemons file descriptor resource cap by adding a *
ulimit* command to the /etc/X11/prefdm file.
After the line PATH=..., add the following line:
ulimit -n 16384
4.
Reboot the system for the changes to take effect.
On Thu, Jun 20, 2013 at 3:46 AM, Philippe BOURDEU d'AGUERRE <
[email protected]> wrote:
> Greg Rodenhiser writes:
>
>> I
>> ask because there are a few times where a SunRay device will be stuck on
>> code 26D and the only way to clear it is to pkill gdm on the host
>> (disruptive to all sessions to clear a single Sunray session).
>>
>
> A softer way is to do:
>
> pkill -9 gdm-binary
>
> It doesn't interrupt current sessions.
> --
> Philippe BOURDEU d'AGUERRE
> AIME - Campus de l'INSA http://www.aime-toulouse.fr/
> 135 av. de Rangueil Tél +33 561 559 885
> 31077 TOULOUSE Cedex 4 - FRANCE Fax +33 561 559 870
> ______________________________**_________________
> SunRay-Users mailing list
> [email protected]
> http://www.filibeto.org/**mailman/listinfo/sunray-users<http://www.filibeto.org/mailman/listinfo/sunray-users>
>
--
Greg Rodenhiser
Technical Services Engineer
College of the Holy Cross
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
