On 6/3/07, Dale <[EMAIL PROTECTED]> wrote:
deface wrote:
> ' /etc/init.d/xdm restart '
> This would restart your login manager, assuming your running one.
> (gdm/kdm/xdm/slim)
>
> I would recommend on finding out the root of your X locking up, rather
> than actually trying to band-aid it.
>
> deface
>
> On Jun 3, 2007, at 8:22 PM, Dale wrote:
>
>>
>> Or, you can do a /etc/init.d/xdm restart . Either should work.
>>
>> On another note, you may want to find out why it is locking up. This
>> should not be happening. Are you sure it is locked up or could it be
>> that what you are doing is just using all the CPU processes and it is
>> to busy to respond?
>>
>> Maybe some serious guru will come in with a plan.
>>
>> Dale
>>
>> :-) :-) :-)
>>
>>
>> --
>> www.myspace.com/-remove-me-dalek1967
>>
>> Copy n paste then remove the -remove-me- part.
>
If he does that, it will restart X. I have also seen where a few others
made the suggestion too. This has always worked for me at least.
Dale
:-) :-) :-)
--
www.myspace.com/-remove-me-dalek1967
Copy n paste then remove the -remove-me- part.
--
Thanks for all the ideas. I'll keep them handy for the next time (it
usually happens
about once or twice a month).
In the meanwhile, a couple of notes:
1) Yes, it's REALLY locked up. But there's always enough CPU left
for a non-X login from another machine. It has to be another machine
because I can't even switch to a console terminal.
2) I have no clue how to find out what's causing the lockup. I'd
love to, because I usually lose a bunch of work in the crash.
3) I don't see anything labeled "SysReq" on my keyboard, but it's
associated with the PrintScreen key on my wife's box. Can I hope
alt-printscreen-K will work? (I personally wonder about it since
_nothing_ else on the keyboard works, but maybe the kernel can see
it).
Again, thanks. I'll say more when it happens again.
--
Kevin O'Gorman, PhD
--
[EMAIL PROTECTED] mailing list
