On Tue, Aug 24, 2010 at 8:36 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
I'm actually working to integrate a new HD monitor in a system built before HD was invented.  The monitor works better than the old one, but just in 4:3 aspect mode.  But that's another thread, I only mention it so you know I'm as well off as I was before the old monitor fritzed out on me.

In order to make progress on this thing, it's useful to be able to control the display manager.  My problem has been that going to /etc/init.d
and commanding "./xdm stop" seems to work, but has no effect on KDE.  Manually killing kde (ps -ef | grep kde, etc) just starts another one.  I finally figured out that I have to find the 'kdm' process and kill that, then a logoff or Ctl_Alt_BS actually gets rid of X, so I can do things like
"X -configure" and so on.

Oddly, "./xdm start" worked fine, and was responsible for kdm being started.   But isn't it odd that the display "manager" has such weak
control on its "subordinate"?  Big PITA for me.  

Grrrrr.


The reason that some of this was in the past tense is that somehow I've gotten in a situation
where rebooting does _not_ start a display manager.  Fortunately, "./xdm start" still works --
it's just more PITA..


--
Kevin O'Gorman, PhD