Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!news.usenet.ovh!.POSTED!not-for-mail From: JKB Newsgroups: comp.os.vms Subject: Re: simh and xdmcp Date: Mon, 26 May 2025 11:10:27 -0000 (UTC) Organization: NUO - News.Usenet.Ovh Message-ID: References: <87plfxvql3.fsf@atr2.ath.cx> <875xhofwnt.fsf@atr2.ath.cx> Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 26 May 2025 11:10:27 -0000 (UTC) Injection-Info: news.usenet.ovh; posting-account="bejo"; logging-data="3919435"; mail-complaints-to="abuse@usenet.ovh" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:aIR4U/rKXh6MveJogqsKPWayJMo= sha256:rxhJIXLen9py/7JFWLtBQZo3XeWHP6kS9nAqR7fJ5js= Le 25-05-2025, jayjwa a écrit : > JKB writes: > >> $ product show product tcpip >> >> PRODUCT KIT TYPE STATE >> >> DEC VAXVMS TCPIP V5.3-18 Full LP Installed >> ----------------------------------- ----------- ------------ > That looks like the Compaq one. > >> I have tried with Xnest with the same result: >> >> $ set display/create/node=192.168.10.103/transport=tcpip/server=1 >> $ show display >> >> Device: WSA17: [super] >> Node: 192.168.10.103 >> Transport: TCPIP >> Server: 1 >> Screen: 0 > You shouldn't have to set the display. That's the job of XDM. You only > have to do that if you rlogin/telnet or similar. Yes, I know. Goal is to use xdmcp, but I'm trying in a first time to display a single window on Xephyr or Xnest. >> I will try xdm /after/ I'm able to display clock on Xnest/Xephyr. I >> don't understand why VMS answers "can't open display"... > I guess I'm confused then, because your subject mentioned xdmcp. I > though you were using XDM. > > If you are doing it "by hand", then just start Xnest/Xephyr with "-ac" > to turn off access control. From the VMS side, you can execute something > like this: > > $ type xephyr.com > $! Command procedure to send X11 traffic to a Xephyr > $! nested XServer, by setting the DISPLAY. > $ SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE=192.168.20.1/SERVER=1/PERMANENT > $ DEFINE/SYSTEM DECW$DISPLAY 'F$TRNLNM("DECW$DISPLAY") > $ RUN SYS$SYSTEM:DECW$STARTLOGIN.EXE > $ > > SERVER corresponds with what Unix calls the :1.0 part of DISPLAY > (matching the above example). Chances are you main desktop is :0.0, so > Xnest/Xephr would then be :1.0. 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 enable XDM, you don't have to run the above each time, and you'll > get a log file to check if something doesn't go right. > > TCPIP> show service xdm /full > > Service: XDM > State: Enabled > Port: 177 Protocol: UDP Address: 0.0.0.0 > Inactivity: 0 User_name: TCPIP$XDM Process: TCPIP$XDM > Limit: 1 Active: 0 Peak: 0 > > File: TCPIP$SYSTEM:TCPIP$XDM_RUN.COM > Flags: None > > Socket Opts: Rcheck Scheck > Receive: 0 Send: 0 > > Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr > File: SYS$SPECIFIC:[TCPIP$XDM]TCPIP$XDM_RUN.LOG > > Security > Reject msg: not defined > Accept host: 0.0.0.0 > Accept netw: 0.0.0.0 > TCPIP> exit $ tcpip TCPIP> show service xdm /full Service: XDM State: Enabled Port: 177 Protocol: UDP Address: 0.0.0.0 Inactivity: 0 User_name: TCPIP$XDM Process: TCPIP$XDM Limit: 1 Active: 0 Peak: 0 File: TCPIP$SYSTEM:TCPIP$XDM_RUN.COM Flags: None Socket Opts: Rcheck Scheck Receive: 0 Send: 0 Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr File: SYS$SPECIFIC:[TCPIP$XDM]TCPIP$XDM_RUN.LOG Security Reject msg: not defined Accept host: 0.0.0.0 Accept netw: 0.0.0.0 TCPIP> > $ type SYS$SPECIFIC:[TCPIP$XDM]TCPIP$XDM_RUN.LOG > $ Set NoOn > $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) > 12-MAY-2025 14:49:57.83 - Waiting for DECwindows to start... > 12-MAY-2025 14:50:02.83 - Waiting for DECwindows to start... > 12-MAY-2025 14:50:07.83 - Waiting for DECwindows to start... > %SYSTEM-S-NORMAL, normal successful completion > %SYSTEM-S-NORMAL, normal successful completion > %SYSTEM-S-NORMAL, normal successful completion > %SYSTEM-S-NORMAL, normal successful completion > %SYSTEM-S-NORMAL, normal successful completion > %SYSTEM-S-NORMAL, normal successful completion > $ > In SYS$SPECIFIC:[TCPIP$XDM]TCPIP$XDM_RUN.LOG, I have a lot of %SYSTEM-S-NORMAL, normal successful completion %NONAME-F-NOMSG, Message number 00000004 Best regards, JB -- Si votre demande me parvient en code 29, je vous titiouillerai volontiers une réponse.