1 |
Stefan G. Weichinger wrote: |
2 |
> walt schrieb: |
3 |
> |
4 |
>> On 11/03/2009 12:31 PM, Stefan G. Weichinger wrote: |
5 |
>> |
6 |
>>> walt schrieb: |
7 |
>>> |
8 |
>>>> Perhaps you have something left over from your gnome session |
9 |
>>>> that doesn't stop when it should. I see that quite often. |
10 |
>>>> |
11 |
>>> hmm, any idea how to find that? |
12 |
>>> |
13 |
>> I use ps ax to see the running processes. Sometimes I see apps |
14 |
>> obviously related to gnome still running after I exit X. I have |
15 |
>> no idea why, but if I plan to restart X I kill those processes |
16 |
>> first. |
17 |
>> |
18 |
>> In your case I would do "ps ax > pre" after a reboot, and then |
19 |
>> after logging out of X do "ps ax > post", and then compare 'pre' |
20 |
>> to 'post' to see what has changed. |
21 |
>> |
22 |
> |
23 |
> Will try something like that asap ... drown in work right now :-) |
24 |
> |
25 |
> S |
26 |
> |
27 |
> |
28 |
> |
29 |
|
30 |
Unrelated in a way but still, I notice that when I go to single user |
31 |
mode that a lot of KDE processes are still running. Sometimes there is |
32 |
a half dozen or so, sometimes a little more or less. I always run "ps |
33 |
aux | less" and page my way through them and use kill to get rid of |
34 |
them. I have always been curious as to why programs don't kell their |
35 |
own processes and clean up after themselves better? This may not just |
36 |
gnome since I use KDE. |
37 |
|
38 |
Dale |
39 |
|
40 |
:-) :-) |