Re: [newbie] Re: X lockup
Ctrl-Alt-Backspace shuts down X It's supposed to, but it took maybe an hour for it to respond. Usually it's instant, but it wasn't in this case. A second is more like it. You've got something stealing cycles in a big way! The problem is that a _lot_ of different things can cause these temporary lockups in which the only thing that'll be noticed by the computer is a power failure (intentional or otherwise). Let's see... I had this problem while playing with xfontsel under GNUstep and fvwm2 on a system running Red Hat 5.0. It's probably important that you know that this is on a 486SX/25MHz machine with 24MB actual RAM. There don't appear to be any disk accesses or other little noises indicating anything going under the hood. If any real processing is going on, it's all in RAM. I noticed a fvwm2 error log file in ~/andy today. I read it: It was a huge list of /tmp files it tried deleting but couldn't since I didn't have permission to. I wonder if that has anything to do with these lockups.
Re: [newbie] Re: X lockup
Ctrl-Alt-Backspace shuts down X It's supposed to, but it took maybe an hour for it to respond. Usually it's instant, but it wasn't in this case. A second is more like it. You've got something stealing cycles in a big way! The problem is that a _lot_ of different things can cause these temporary lockups in which the only thing that'll be noticed by the computer is a power failure (intentional or otherwise). Let's see... I had this problem while playing with xfontsel under GNUstep and fvwm2 on a system running Red Hat 5.0. It's probably important that you know that this is on a 486SX/25MHz machine with 24MB actual RAM. There don't appear to be any disk accesses or other little noises indicating anything going under the hood. If any real processing is going on, it's all in RAM. I noticed a fvwm2 error log file in ~/andy today. I read it: It was a huge list of /tmp files it tried deleting but couldn't since I didn't have permission to. I wonder if that has anything to do with these lockups. Does your system stay running long enough for the cron jobs to process? You could have a ton of temp files and stuff waiting to be dumped. Brian
Re: [newbie] Re: X lockup
Does your system stay running long enough for the cron jobs to process? I haven't done anything with cron. I have yet to read about what it's for. You could have a ton of temp files and stuff waiting to be dumped. Should I just rm everything out of the /tmp directory?
Re: [newbie] Re: X lockup
I still want to know how to shut either X or the process down instantly. Ctrl-Alt-Backspace shuts down X It's supposed to, but it took maybe an hour for it to respond. Usually it's instant, but it wasn't in this case.
Re: [newbie] Re: X lockup
Ctrl-Alt-Backspace shuts down X It's supposed to, but it took maybe an hour for it to respond. Usually it's instant, but it wasn't in this case. A second is more like it. You've got something stealing cycles in a big way!
[newbie] Re: X lockup
On my PC, X appears to have locked up. It's running what I think is AfterStep. I started xfontsel and poked around a couple of fonts, but now it's just sitting. It doesn't seem to respond to anything: the mouse, Alt+F2, Ctrl+Alt+BkSp, Ctrl+Alt+Del, or anything else I know of. I do NOT want to use the power switch to get out of this one! This system uses Red Hat 5.0. What can I do? Update: I went back to the computer and found that X had shut down. Apparently it buffered all of my input but decided to wait an hour to process it. I still want to know how to shut either X or the process down instantly.
Re: [newbie] Re: X lockup
I still want to know how to shut either X or the process down instantly. Ctrl-Alt-Backspace shuts down X
