Subject: | |
From: | |
Reply To: | |
Date: | Sat, 13 Nov 2021 22:14:36 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Sorry, my customer is bound to SL 6.10, a medical programm is only
supported under 6.10 (and ubuntu 20.04) , a new server was just
installed 2 months ago for 25 linux workstations (XDMCP linux clients,
Win10 with NX ). Thats the server for next 5-7 years!! No update
possible, special features for userfriendly communication with medical
server in internet only supported under 6.10. , NOT 7.x , 8.X!!
Once again: who has idea why nxserver 3.2.0-74 is locked/ blocked?
tia
Am 13.11.21 um 21:08 schrieb Nico Kadel-Garcia:
> On Sat, Nov 13, 2021 at 2:22 PM Ekkard Gerlach <[log in to unmask]> wrote:
>> Hello,
>>
>> using SL 6.10, nxserver 3.2.0-74 .
> Stop there. Update to SL 7 if you expect contemporary tools to work or
> continue to work: the underlying RHEL 6 from upstream The final
> release of RHEL 6 was more than 3 years ago.
>
> Nico Kadel-Garcia
>
>> root@arthur:~# export DISPLAY=10.0.0.9:1002.0
>> Sie haben neue Post in /var/spool/mail/root.
>> root@arthur:~# xterm
>> Warning: This program is an suid-root program or is being run by the root user.
>> The full text of the error or warning message cannot be safely formatted
>> in this environment. You may get a more descriptive message by running the
>> program as a non-root user or by removing the suid bit on the executable.
>> xterm Xt error: Can't open display: %s
>>
>> but:
>> root@arthur:~# export DISPLAY=:1002.0
>> root@arthur:~# xterm
>> Warning: Cannot convert string "nil2" to type FontStruct
>> xterm: cannot load font -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1
>>
>> works!! (xhost + is in autostart of every user).
>>
>>
>> Why not accessible viel IP/ network? Only accessible local? What is locked on scientific?
>>
>>
>> example:
>>
>> --pc44 30755 0.0 0.4 180096 120300 ? S 10:00 0:10 _ /usr/libexec/nx/nxagent -persistent -D -name NX - pc44@arthur:1002 - DavidX (GPL Edition) -option /home/pc44/.nx/C-arthur-1002-27736AF6397123CD7F3F645BCA8E28A4/options -nolisten tcp :1002
>>
>>
>> nxstarts with "-nolisten tcp". Where is that set? - In /etc/nxserver/node.conf:
>>
>> #AGENT_EXTRA_OPTIONS_X="-nolisten tcp" # is commented out!!
>>
>> When I modify it to
>>
>> AGENT_EXTRA_OPTIONS_X="-listen tcp" # nolisten -> listen!
>>
>> Then nxserver doesn't allow any login, aborts with error message
>>
>> Error: Aborting session with 'Unrecognized option: -listen'.
>>
>>
>> anybody here can help?
>>
>> Some security policy on SL 6.10 that forces nxserver to "-nolisten tcp" ?
>>
>> Or: who or what forces to start nx with "-nolisten tcp" although its not commented in in node.conf?
>>
>>
>> tia
>>
>> Ekkard
|
|
|