dt issue

[Jon Talbot]

We have a B2000 workstation that is used via the network without a locally connected keyboard and worktation.

This machine was recently rebuilt using an ignite image from a workstion that did contain a keyboard and mouse.

Since the rebuild the users can't display x-session back to their machines using exceed (using the xdmcp protocol)

The machine has errors in /var/dt/Xerrors:

**********************************************

cvhp162# more Xerrors

^[gXIO: fatal IO error 232 (Connection reset by peer) on X server "cvhp162:0.
0"
after 0 requests (0 known processed) with 0 events remaining.

Fatal server error:
Couldn't open X pointer device! Is one attached?

^[gXIO: fatal IO error 232 (Connection reset by peer) on X server "cvhp162:0.
0"
after 0 requests (0 known processed) with 0 events remaining.

**********************************************

We have come to the conclusion that the workstation is not displaying back because of the mouse being missing.

We don't want to plug a mouse in the back and we do'nt want to reinstall.

How can we get around this problem? I have looked at /etc/dt/config/* but their is nothing obvious to edit, also looking around on itrc and google has'nt yielded anything, any suggestions?

[Peter Nikitka · Accepted solution]

Hi,

the file /var/dt/Xerrors contains messages of the local Xserver. Since you do not need a local Xserver, because your users do not sit in front of that box (and no mouse is attached), I recommend to unconfigure the start (or the attempt of a start) of the local Xserver.

If not existent, copy this config file:
cp /usr/dt/config/Xservers /etc/dt/config/Xservers
(create the directory, if missing!).

Then comment the line looking like
:0 Local ...
in that (new) file.

Nevertheless: the fact, that a local Xserver cannot be started should NOT effect the ability to be a client of a remote Xserver.
There must be something wrong elsewhere.

mfG Peter

[Jon Talbot]

Thanks for your help Peter, I removed
/etc/dt/config/Xconfig

commented everything in

/etc/dt/config/Xservers

restarted dt, and that seemed to do the trick