1 |
' /etc/init.d/xdm restart ' |
2 |
This would restart your login manager, assuming your running one. |
3 |
(gdm/kdm/xdm/slim) |
4 |
|
5 |
I would recommend on finding out the root of your X locking up, |
6 |
rather than actually trying to band-aid it. |
7 |
|
8 |
deface |
9 |
|
10 |
On Jun 3, 2007, at 8:22 PM, Dale wrote: |
11 |
|
12 |
> Stratos Psomadakis wrote: |
13 |
>> O/H Kevin O'Gorman έγραψε: |
14 |
>> |
15 |
>>> From time to time my X server will lock up, usually but not always |
16 |
>>> while I'm editing something in ooffice. It's always something |
17 |
>>> that's |
18 |
>>> pretty heavily graphical. When this happens, the only thing that |
19 |
>>> still works on my desktop is mouse motion. No clicks actually |
20 |
>>> register, and even the three-finger salutes (BS and DEL) are |
21 |
>>> feckless. |
22 |
>>> |
23 |
>>> However, I can SSH into the machine from elsewhere and pretty |
24 |
>>> much do |
25 |
>>> anything else I want. I usually have to reboot the machine, |
26 |
>>> because I |
27 |
>>> haven't figured out how to restart X in gentoo. I'm sure it's |
28 |
>>> pretty |
29 |
>>> simple, but I can't seem to find documentation on this particular |
30 |
>>> thing and it's not like the usual init.d services. Lots on |
31 |
>>> startup, a |
32 |
>>> bit on shutdown, but nothing I see is about restart. |
33 |
>>> |
34 |
>>> When this happens, sometimes X is using 100% of one of the CPU's, |
35 |
>>> but |
36 |
>>> I don't always check and haven't recently verified my impression |
37 |
>>> that |
38 |
>>> sometimes all CPU's are at an idle (I have 4 hyperthreads). |
39 |
>>> |
40 |
>>> Can somebody help me stop and restart X? I'm using kdm for login. |
41 |
>>> |
42 |
>>> |
43 |
>> maybe you can ssh to your machine and then: |
44 |
>> ps -A | grep X |
45 |
>> and see the pid of X... |
46 |
>> and then kill [pid of X]... |
47 |
>> |
48 |
>> |
49 |
> |
50 |
> Or, you can do a /etc/init.d/xdm restart . Either should work. |
51 |
> |
52 |
> On another note, you may want to find out why it is locking up. |
53 |
> This should not be happening. Are you sure it is locked up or |
54 |
> could it be that what you are doing is just using all the CPU |
55 |
> processes and it is to busy to respond? |
56 |
> |
57 |
> Maybe some serious guru will come in with a plan. |
58 |
> |
59 |
> Dale |
60 |
> |
61 |
> :-) :-) :-) |
62 |
> |
63 |
> |
64 |
> -- |
65 |
> www.myspace.com/-remove-me-dalek1967 |
66 |
> |
67 |
> Copy n paste then remove the -remove-me- part. |