I have 2 computers
one is fast and the other one has 19" monitor

I started kdm on both of them, but i can't remotely log on the fast
computer. Is there some options or conf file i should look at ?

Could you recomen me some Howto i cant fing anything about it.

Now i use export DISPLAY after ssh loging.
--
Patryk

Patryk <patrykx@poczta.onet.pl> wrote:
> I started kdm on both of them, but i can't remotely log on the fast
> computer. Is there some options or conf file i should look at ?

Yes, have a look at /opt/kde/share/config/kdm/Xaccess, or maybe it is
located in /etc/X11/xdm instead.

Also make sure that you have something like the following in
/opt/kde/share/config/kdm/kdmrc:

[Xdmcp]
Enable=true
Willing=/opt/kde/share/config/kdm/Xwilling
Xaccess=/opt/kde/share/config/kdm/Xaccess

> Could you recomen me some Howto i cant fing anything about it.

Good places to start would probably be the XDMCP-HOWTO and the
XWindow-User-HOWTO.

> Now i use export DISPLAY after ssh loging.

You shouldn't have to do that, ssh is able to also pass on the DISPLAY.
Make sure that you have the following in sshd_config of your remote
machine:

X11Forwarding yes
X11DisplayOffset 10

Unless you place this in ssh_config of your local machine:

ForwardX11 yes

.... you will have to start ssh with the -X switch.

However, once you have this working you will be able to:

"ssh remoteuser@remotehost" or "ssh -X remoteuser@remotehost" depending on
your ssh_config. Then if you look at your DISPLAY variable you will
probably see something like this:

remotehost:/tmp> env | grep DISPLAY
DISPLAY=remotehost:11.0

You might think that this seems wrong as the DISPLAY points to the remote
host and the number is much higher than the number of displays on that
machine. However, this is the way it is supposed to be. Ssh will take care
of display remotehost:11 and forward it to localhost:0. You don't even
have to use anything like xhost to allow those windows on your display.

However, there is one more feature of ssh. Everything is encrypted.
Sometimes you don't need this encryption and need more speed of the
display. Then you should do it the old way:

xhost +remotehost
ssh remoteuser@remotehost
export DISPLAY=localmachine:0
xclock

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc2(at)uthyres.com Examples of addresses which go to spammers:
info@webrider.ru remove@emailpromo.biz root@localhost

On Sun, 29 Aug 2004 00:02:04 +0200, Henrik Carlqvist wrote:

> You might think that this seems wrong as the DISPLAY points to the remote
> host and the number is much higher than the number of displays on that
> machine. However, this is the way it is supposed to be. Ssh will take care
> of display remotehost:11 and forward it to localhost:0. You don't even
> have to use anything like xhost to allow those windows on your display.
>
> However, there is one more feature of ssh. Everything is encrypted.
> Sometimes you don't need this encryption and need more speed of the
> display. Then you should do it the old way:

I've tried that and definatley i need more speed
I have Athlon 2500 can i speed sshd up ?
On the other hand it's a home lan so i don't need security.

Also when i use ssh some aplication don't work.
Eclipse (it's a IDE written in Java using gtk) crshes while running this
way.

-
Patryk

patryk <patrykx@poczta.onet.pl> wrote:
>> Sometimes you don't need this encryption and need more speed of the
>> display. Then you should do it the old way:
>
> I've tried that and definatley i need more speed

Do you need more speed than the old way? If so, what kind of network do
you have? What kind of application are you running?

> I have Athlon 2500 can i speed sshd up ?

The only way I know of is to manually set DISPLAY and use xhost instead of
encrypting X with ssh.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc2(at)uthyres.com Examples of addresses which go to spammers:
info@webrider.ru remove@emailpromo.biz root@localhost

Henrik Carlqvist wrote:
>>> Sometimes you don't need this encryption and need more speed of the
>>> display. Then you should do it the old way:
> Do you need more speed than the old way? If so, what kind of network do
no the "export DISPLAY method" is ok with speed
> you have? What kind of application are you running?
I have 100Mbit LAN.
When i change windows i seed blach screen for a fraction of second, it
doesn't happen using xhost.

What's the reason of lag using encryption ?
Encryption shouldn't increase amount of data transfrerd throu the
connection.
The cpu load was only about 15%, normaly when is use xhost its about 2%.

--
Patryk

Patryk <patrykx@NOSPAMpoczta.onet.pl> wrote:
> What's the reason of lag using encryption ?

First the remote machine has to use its CPU to encrypt the X network
traffic. Then the local machine uses its CPU to decrypt the traffic. I
have seen that even if both machines are powerful dual CPU machines things
like moving video will be a lot faster.

> Encryption shouldn't increase amount of data transfrerd throu the
> connection.

No, thats true.

> The cpu load was only about 15%, normaly when is use xhost its about 2%.

Did both machines have that load? I suppose that you also have a program
on the remote machine which updates the window and that program consumes
some CPU. Now it has to share that CPU with ssh.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc2(at)uthyres.com Examples of addresses which go to spammers:
info@webrider.ru remove@emailpromo.biz root@localhost