| 1 |
On 08/24/2010 08:36 PM, Kevin O'Gorman wrote: |
| 2 |
> In order to make progress on this thing, it's useful to be able to |
| 3 |
> control the display manager. My problem has been that going to /etc/init.d |
| 4 |
> and commanding "./xdm stop" seems to work, but has no effect on KDE. |
| 5 |
> Manually killing kde (ps -ef | grep kde, etc) just starts another one. |
| 6 |
> I finally figured out that I have to find the 'kdm' process and kill |
| 7 |
> that, then a logoff or Ctl_Alt_BS actually gets rid of X, so I can do |
| 8 |
> things like |
| 9 |
> "X -configure" and so on. |
| 10 |
|
| 11 |
You ~should~ be able to log onto a console vty by using Ctrl-Alt-Fn |
| 12 |
(where n=1-6). You can then log on from there and commence all manner of |
| 13 |
Gentacular shelly goodness. |
| 14 |
|
| 15 |
There's really no need to kill the display manager ever. In fact, you |
| 16 |
can have more than one running at a time. |
| 17 |
|
| 18 |
> Oddly, "./xdm start" worked fine, and was responsible for kdm being |
| 19 |
> started. But isn't it odd that the display "manager" has such weak |
| 20 |
> control on its "subordinate"? Big PITA for me. |
| 21 |
|
| 22 |
Yeah, that's just a semantic problem, really. The generic term is "xdm" |
| 23 |
but depending upon your setup, you can plug in any display manager. |
Archives