A short explanantion is in order here... Since you seam to be missing an small piece of the puzzle.... 8-) SuSe has forseen your need and prepared thier scripts to allow you an easy way to change the values.... go to yast->system->/etc/sysconfig editor. there search for DISPLAYMANAGER Select the "$DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN" set to yes, Click Finish... Now not only does it work, but the value will be correctly use after each update, and SuSE will try (they make no garuntees) to keep this implemented in new version of XWindows as well. SuSE is your friend an helper, if you let them.... Jerry On Sat, 2004-05-29 at 09:16, John Andersen wrote:

On Friday 28 May 2004 23:03, Mark Gray wrote:

...

John Andersen writes:

...

On Friday 28 May 2004 22:23, Mark Gray wrote:

...

Actually you need to change a line in /etc/sysconfig/displaymanager or SuSEconfig will rewrite the file every time it is called: (KDE is almost unusably slow as it is, using ssh -X is laughable).

No, you don't have to touch that, it works with no change.

Sorry to disagree, but I only discovered the configuration variable after SuSEconfig had changed it back several times (take a look at the guilty code in /sbin/conf.d/SuSEconfig.xdm

root@k6:~ # grep -5 nolisten /sbin/conf.d/SuSEconfig.xdm check_md5_and_move $file else echo "${0##*/}: change of $file skipped" fi if test "$DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN" = "no" ; then sed "s/\(.*\/usr\/X11R6\/bin\/X\)[ \t]*\(-nolisten[ \t]*tcp[ \t]*\|\)/\1 -nolisten tcp /g" < $file > ${file}.SuSEconfig check_md5_and_move $file elif test "$DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN" = "yes" ; then sed "s/\(.*\/usr\/X11R6\/bin\/X\)[ \t]*-nolisten tcp[ \t]*/\1 /g" < $file > ${file}.SuSEconfig check_md5_and_move $file else echo "${0##*/}: change of $file skipped" fi fi

Perhaps I misunderstood...

I thought you were saying you had to change that line in /etc/sysconfig/displaymanager in order to forward X over ssh. Perhaps you meant that change was necessary for a remote xterm NOT using ssh. (Meby so, I never tried that).

You don't have to make that change to run X over ssh. Mine still says this: # # Tcp port 6000 of Xserver. When set to "no" (default) Xserver is # started with "-nolisten tcp". Only set this to "yes" if you really # need to. Use ssh X11 port forwarding whenever possible. # DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="no"

And yet I can open an xterm over an ssh connection just fine, but it won't listen for a remote connections on port 6000.

-- _____________________________________ John Andersen