Hi Olaf, That sounds interesting. I have a follow question regarding this subject, as I just plan to introduce SuSE9/KDE as Session server to replace my existing CDE session server on a network. That way I can dedicate my somewhat tired Sun Solaris workgroup server as a remote execution host for a primary X application. (This is also posted as another subject on this list without any response yet). The principle is illustrated in the online CDE guides on Sun Docs: http://docs.sun.com/db/doc/802-5818/6i9i51als?q=session+host&a=view http://docs.sun.com/db/doc/802-5818/6i9i51am0?q=session+host&a=view Where is the corresponding KDE/KDM configuration documentation for network displays, possibly beyond the Howto's? Does KDE/KDM (as CDE does) work with the Xaccess control file for XDMCP connections and its counterpart Xservers to query for remote login manager(s)? TIA/Terje Olaf Lenz skrev:
Hello!
This is not a question, just something I noticed during the last days when I tried to configure KDM on a SuSE Linux 9.0 Pro Machine to fit my needs, and which may help some people to find the problem...
First I noticed that changing
Yast2 -> Security and Users -> Security Setting -> Allow Remote Graphical Login
did not have any effect. The same with the /etc/sysconfig-Editor (Desktop -> Display Manager -> DISPLAYMANAGER_REMOTE_ACCESS).
Finally I found out, why:
1. Before I did this, I used the KDE Control Center to modify the settings of KDM (System Administration -> Login Manager). This will modify
/etc/opt/kde3/config/kdm/kdmrc
2. When you now use YaST2 to change the remote graphical login, SuSEconfig will try to modify kdmrc as well, but it won't as it was changed by another program. Calling SuSEconfig by hand will show you an appropriate warning:
------------
SuSEconfig [clip] Executing /sbin/conf.d/SuSEconfig.kdm3...
ATTENTION: You have modified /etc/opt/kde3/share/config/kdm//kdmrc. Leaving it untouched... You can find my version in /etc/opt/kde3/share/config/kdm//kdmrc.SuSEconfig... [clip] ------------
3. Unfortunately, when you use YaST2, you will get no warning whatever.
So what you need to do is to edit the kdmrc by hand (with an editor of your choice) and set "Enable=true" in the [Xdmcp]-section.
I think this is a bug, and I reported it to the SuSE-Feedback.
This problem did cost me a few hours to work out, so I hope that someone else may find it faster because I wrote this message...
Cheers Olaf