Karl Rossing wrote:
On 08/25/2011 05:40 AM, Hagen Heiduck wrote:
However, I found other situations where gdm's main process is getting
stuck. Without going in too much details, this appears when gdm shows
a warning message like "Your session only lasted less than 10
seconds", or a hint like "This is the Failsafe XYZ session" after a
failsafe session has been started. Under such circumstances gdm is
becoming unresponsive and one can observe messages like
"Your session only lasted less than 10 seconds" will sit on the screen
all day until ok is clicked. The same thing for the is the Failsafe
session.
gdm-binary[21542]: [ID 702911 daemon.warning] DEBUG: Timeout occurred
for sending message WRITE_X_SERVERS 21542 0
which results in our beloved 26D status. This is reproducible (under
OpenSolaris 2009.06) and vanishes, when the causing message is gone
again.
So how do you end up finding these kiosk sessions and terminating them
proactively?
I do it the other way, by trying to avoid them. If your session returns
with exit code 66, that message does not appear (s. 'man gdm-binary').
Hagen
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
