On 01/13/11 19:57, Karl Rossing wrote:
Would the issue i'm seeing be CR# 6623505?
We can't know the answer to this without some of the information I requested.
-Bob
If so, I'll have to figure out how to place an IDR.
On 01/04/11, *Bob Doolittle *bob.doolit...@oracle.com wrote:
Well then
Would the issue i'm seeing be CR# 6623505?If so, I'll have to figure out how to place an IDR.On 01/04/11, Bob Doolittle bob.doolit...@oracle.com wrote:Well then there you go. The associated session is on Server 2, display 5. If you just want to clean the situation up, you can try a couple of
On 01/04/11 10:43, Karl Rossing wrote:
utdesktop -lw will show me desktops that are in an errored state.
How can I find out a process id for the errored session?
When you see DTUs in this state, do they show up anywhere with utwho -c? If
so, that should indicate the display number. You
Perhaps we can help. Can you answer my question please? Does utwho -ac on any of the
servers show the DTUs which are reported by utdesktop -lw?
-Bob
On 01/04/11 11:27, Karl Rossing wrote:
What I'm trying to do is to proactively find dtu's that are showing 26d.
I have 110 DTU's on 3 servers
Hello Karl,
If you are running a policy were only card users have access to the Sun
Ray than be aware of:
CR# 6623505 utwho doesn't list the DTUs showing yuvicons
As far as I know this can only be fixed with an IDR at this time.
If you are not using this policy than you don't have to worry
Well then there you go. The associated session is on Server 2, display 5. If
you just want to clean the situation up, you can try a couple of things:
1 Is there an Xnewt running for display :5 (the display number is visible on
the command line via ps)?
2 If you reset the DTU, does the problem
