dove@savax.UUCP (webster dove) (08/04/87)
We have a Sun 3/110 and 3/160 and Ultrix vax and we use xinit to start up X and it (typically) restores the keyboard when X exits. Occasionally, when xinit breaks, the Sun is left with the keymap broken (type '\b' see '+'). This state is as described in earlier msgs about keyboard problems. What I just noted is that the X server on the Masscomp, which can't talk to the other three machines behaves this same way. When running clients on the Masscomp, to the Masscomp server everything is fine, but either from the Masscomp to Sun or to vax and the other way around, the connection acts as though the keyboard were broken (type '\b' see '+'). Is there some option or definition that would cause this miscommunication regardless of whether the client or server end were on the Masscomp??