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