John Andersen
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
And I also have acceptable performance with X over ssh, precisely because it DOES compress the transmission. On local networks, or fast wide area networks its actualy faster than running locally because you have two processors involved. All the hard work for X is offloaded to the machine where you sit, and all the other work is done on the remote machine.
To give ssh and KDE their due, I tend to keep using computers which most people would consider obsolete, and 9.1's KDE is right on the edge of needing to be replaced by something faster on my "antiques" :-)