Re: simh and xdmcp

Liste des GroupesRevenir à co vms 
Sujet : Re: simh and xdmcp
De : JKB (at) *nospam* hilbert.invalid (JKB)
Groupes : comp.os.vms
Date : 27. May 2025, 07:12:22
Autres entêtes
Organisation : NUO - News.Usenet.Ovh
Message-ID : <slrn103alu6.6kn.JKB@hilbert.systella.fr>
References : 1 2 3 4 5 6
User-Agent : slrn/1.0.3 (Linux)
Le 26-05-2025, jayjwa <jayjwa@atr2.ath.cx.invalid> a écrit :
JKB <JKB@hilbert.invalid> writes:
>
On Linux side, I use :
$ Xephyr -ac :1 -screen 1024x768 -listen tcp -query 192.168.10.107
>
On VMS side:
$ set display/create/node=192.168.10.103/transport=tcpip/server=1
$ DEFINE/SYSTEM DECW$DISPLAY 'F$TRNLNM("DECW$DISPLAY")
$ RUN SYS$SYSTEM:DECW$STARTLOGIN.EXE
$
>
No error, but startlogin doesn't appear on Xephyr.
>
$ mcr sys$system:decw$clock
X Toolkit Error: Can't Open display
%DWT-F-NOMSG, Message number 03AB8204
>
If you want to do it "by hand" as above, leave off everything from
"-query" onward, including IP address. If you want to use XDM, use the
-query flag with IP and don't run any procedure on the VMS side. You're
mixing two different things: you're telling Xephyr to contact an X
Display Manager at 192.168.10.107 and then trying to manually start
another session on top of 192.168.10.103:1.0

OK.

Let consider :
- hilbert (Linux Workstation) that runs Xephyr, 192.168.10.103 ;
- legendre (NetBSD server), 192.168.10.128 ;
- fermat (VAX, OpenVMS 7.3), 192.168.10.107.

Hilbert runs Xephyr -ac :1 -screen 1024x768 -listen tcp. On
legendre, export DISPLAY=hilbert:1.0 && xterm launches xterm on
Xephyr display as expected.

Now, on VMS side:
$ tcpip
TCPIP> ping hilbert
PING hilbert.systella.fr (192.168.10.103): 56 data bytes
64 bytes from 192.168.10.103: icmp_seq=0 ttl=64 time=20 ms
 Cancel
----hilbert.systella.fr PING Statistics----
1 packets transmitted, 1 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 20/20/20 ms
TCPIP> exit
$ set display/create/node=192.168.10.103/transport=tcpip/server=1
$ show display
 
    Device:    WSA21:  [super]
    Node:      192.168.10.103
    Transport: TCPIP
    Server:    1
    Screen:    0
 
$ mcr sys$system:decw$clock
X Toolkit Error: Can't Open display
%DWT-F-NOMSG, Message number 03AB8204
$

I don't understand difference between BSD export DISPLAY && xterm
and VMS set/display followed by mcr. There is no firewall on LAN.

Best regards,

JB

--
Si votre demande me parvient en code 29, je vous titiouillerai volontiers
une réponse.

Date Sujet#  Auteur
23 May 25 * simh and xdmcp17JKB
23 May 25 +* Re: simh and xdmcp2Simon Clubley
25 May 25 i`- Re: simh and xdmcp1JKB
24 May 25 `* Re: simh and xdmcp14jayjwa
25 May 25  `* Re: simh and xdmcp13JKB
25 May 25   +* Re: simh and xdmcp3Lawrence D'Oliveiro
25 May 25   i`* Re: simh and xdmcp2Arne Vajhøj
25 May 25   i `- Re: simh and xdmcp1Lawrence D'Oliveiro
25 May 25   `* Re: simh and xdmcp9jayjwa
26 May 25    `* Re: simh and xdmcp8JKB
26 May 25     `* Re: simh and xdmcp7jayjwa
27 May 25      `* Re: simh and xdmcp6JKB
27 May 25       +* Re: simh and xdmcp3Simon Clubley
27 May 25       i`* Re: simh and xdmcp2JKB
27 May 25       i `- Re: simh and xdmcp1Lawrence D'Oliveiro
27 May 25       `* Re: simh and xdmcp2jayjwa
1 Jun 25        `- Re: simh and xdmcp1JKB

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal