On Tuesday 13 July 2004 11:28, Alexandr Malusek wrote:

Jarod Wilson writes:

...

...

From another message, I saw a reference to using: x -query hostname - to get into a remote X session. All that happens is I get a full screen X session (shows the pretty X cursor with the "checkered" background) but nothing happens.

What am I missing?

You have some edits to make to config files on the SuSE machine. Remote X isn't permitted by default (because of security implications). I basically followed this:

http://www.tldp.org/HOWTO/XDMCP-HOWTO/

This document is rather long and obsolete.

True, much of it is noise. The actual process was a few quick edits, one in /etc/X11/xdm/Xaccess, one in /etc/rc.d/init.d/xfs and one in /etc/X11/fs/config.

It may be enough to set DISPLAYMANAGER_REMOTE_ACCESS="yes" in /etc/sysconfig/displaymanager, run SuSEconfig, and restart kdm. Do all three steps on the server, YaST2 can be used for the first two steps.

Didn't know about that route. That would be even easier... -- Jarod C. Wilson, RHCE jcw@wilsonet.com

On Wednesday 14 July 2004 11:05, Anders Johansson wrote:

On Tuesday 13 July 2004 21.34, Jarod Wilson wrote:

...

True, much of it is noise. The actual process was a few quick edits, one in /etc/X11/xdm/Xaccess,

This isn't used, the one in /etc/opt/kde3/share/config/kdm is, and it doesn't have to be touched

...

one in /etc/rc.d/init.d/xfs and one in /etc/X11/fs/config.

xfs, to the best of my knowledge, isn't used at all anymore And you missed the big one, kdmrc, section [Xdmcp], set Enable=True

I hope no one is still using regular xdm anymore

Apparently, my memory fails me (not at all a surprise). Now that you mention it, I do recall editing some stuff in /etc/opt/kde3... And I recall finding it rather annoying that there were six different kdmrc files, and it wasn't entirely obvious which one did what. $ locate kdmrc /etc/opt/kde3/share/config/kdm/kdmrc /etc/opt/kde3/share/config/kdm/kdmrc.SuSEconfig /opt/kde3/share/config/kdm/kdmrc /opt/kde3/share/config/SuSE/default/kdmrc /opt/kde3/share/doc/HTML/en/kdm/kdmrc-ref.docbook /var/adm/SuSEconfig/md5/etc/opt/kde3/share/config/kdm/kdmrc Not sure on xfs, I'd have to assume you know better than me. I can't even properly remember what I edited. But I'm not using xdm. :-) -- Jarod C. Wilson, RHCE jcw@wilsonet.com

On Wednesday 14 July 2004 11:22, Anders Johansson wrote:

On Wednesday 14 July 2004 20.16, Jarod Wilson wrote:

...

/etc/opt/kde3/share/config/kdm/kdmrc /opt/kde3/share/config/kdm/kdmrc

These two should be the same, the one in /opt should be a symlink to the one in /etc/opt if your installation is healthy

Hm... This was a clean install, and those two files are distinct (and different)... # ll /opt/kde3/share/config/kdm/ -rw-r--r-- 1 root root 17940 2004-06-22 11:00 kdmrc # ll /etc/opt/kde3/share/config/kdm/ -rw-r--r-- 1 root root 17872 2004-06-22 10:58 kdmrc I'll have to take a look at one of my SuSE boxes I *haven't* tried manually hacking for remote X...

...

/etc/opt/kde3/share/config/kdm/kdmrc.SuSEconfig

This is a version created by SuSEconfig because you had manually edited kdmrc. SuSEconfig won't overwrite your edits, it will create its own copy where you can pick out whatever changes you want to use in your custom version

...

/opt/kde3/share/config/SuSE/default/kdmrc

This is the template SuSEconfig uses as a starting point when it generates its new version

...

/var/adm/SuSEconfig/md5/etc/opt/kde3/share/config/kdm/kdmrc

This is an md5sum of kdmrc that SuSEconfig uses to determine if you have made manual changes

Thank you for the clarification! All makes much more sense now.

...

/opt/kde3/share/doc/HTML/en/kdm/kdmrc-ref.docbook

This is documentation

Shoulda snipped that one out. No confusion there. -- Jarod C. Wilson, RHCE jcw@wilsonet.com Got a question? Read this first... http://catb.org/~esr/faqs/smart-questions.html MythTV, Fedora Core & ATrpms documentation: http://wilsonet.com/mythtv/ MythTV Searchable Mailing List Archive http://www.gossamer-threads.com/lists/mythtv/

On Tuesday 13 July 2004 19:28, John Andersen wrote:

On Tuesday 13 July 2004 09:28 am, Jarod Wilson wrote:

...

On Tuesday 13 July 2004 06:53, Steve Kratz wrote:

...

Ok, Cygwin's installed on my Windoze PC. A fairly stock SuSE 9.1 is installed on my laptop. I can ssh into that box with standard SSH.

From another message, I saw a reference to using: x -query hostname - to get into a remote X session. All that happens is I get a full screen X session (shows the pretty X cursor with the "checkered" background) but nothing happens.

What am I missing?

You have some edits to make to config files on the SuSE machine. Remote X isn't permitted by default (because of security implications). I basically followed this:

Wait a minute,,, He said he connected by ssh, therefore his X session would not be a remote session but rather a local session.

Read both of the OP's paragraphs. He said he connected by ssh, but also that he'd seen reference to using X - query hostname to get a remote X session, and was interested in making that work. -- Jarod C. Wilson, RHCE jcw@wilsonet.com

On Wednesday 14 July 2004 20.37, John Andersen wrote:

On Wednesday 14 July 2004 09:56 am, Jarod Wilson wrote:

...

...

Wait a minute,,, He said he connected by ssh, therefore his X session would not be a remote session but rather a local session.

Read both of the OP's paragraphs. He said he connected by ssh, but also that he'd seen reference to using X - query hostname to get a remote X session, and was interested in making that work.

Still no need to hack X settings, as it STILL will be considdered a LOCAL x session by the remote box (because it sees it as originating from 127.0.0.1.

What does that mean?

Try this ssh -X -T user@some.host.com xterm

Why -T? Why not simply ssh -X user@some.host.com get a shell, and run the apps, with a few more bytes bandwidth not consumed by the superfluous xterm.

On Wednesday 14 July 2004 11:37, John Andersen wrote:

On Wednesday 14 July 2004 09:56 am, Jarod Wilson wrote:

...

...

Wait a minute,,, He said he connected by ssh, therefore his X session would not be a remote session but rather a local session.

Read both of the OP's paragraphs. He said he connected by ssh, but also that he'd seen reference to using X - query hostname to get a remote X session, and was interested in making that work.

Still no need to hack X settings, as it STILL will be considdered a LOCAL x session by the remote box (because it sees it as originating from 127.0.0.1.

Try this ssh -X -T user@some.host.com xterm

And that STILL doesn't address the OP's question about getting X -query hostname to work. ssh'ing to the machine with X11 forwarding enabled and launching an xterm isn't anywhere near the same thing as a full remote X KDE session into the remote machine. -- Jarod C. Wilson, RHCE jcw@wilsonet.com

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 14 July 2004 23:43, John Andersen wrote:

On Wednesday 14 July 2004 11:18 am, Jarod Wilson wrote:

...

...

ssh -X -T user@some.host.com xterm

And that STILL doesn't address the OP's question about getting X -query hostname to work. ssh'ing to the machine with X11 forwarding enabled and launching an xterm isn't anywhere near the same thing as a full remote X KDE session into the remote machine.

No, its not, but again, I was using xterm merely as an example and I did mention that you could start any X application.

Including /opt/kde3/bin/startkde if you want a full screen KDE session remotely.

Yes, I realize it did not answer his question about query hostname as the thread had taken a turn from that (obviating the need to do so with ssh).

I don't quite entirely follow here, I thought the thread took a turn *to* X - -query, not away from it, but...

Its ok Jarod, the people wanting this advice have already replied off list, just ignore my nattering....

...as long as everyone has the information they're after, all is well that ends well. I tend not to ignore anything anyone says if I'm into the topic. - -- Jarod C. Wilson, RHCE jcw@wilsonet.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA9j7xln8CX+oYdJURAqv2AKCFXgo4n4UVLuV4i0m98o4HjAapkACePLNP AW23JCaDaFc5SyUUt50912o= =XRs5 -----END PGP SIGNATURE-----

On Friday 16 July 2004 03:10 pm, Hipolito A. Gonzalez M. wrote:

I did all. Put the port in 177 or 0 And change in /opt/kde3/..........

But nothing!

When you make your ssh connection, add to the end of the connection line the command you want to run, such as /opt/kde3/bin/startkde -- _____________________________________ John Andersen