On Monday 13 January 2003 22:14, Kevin McLauchlan wrote:
On Monday 13 January 2003 14:05, Dylan wrote:
Do you have facilities to log in remotely? If you can, then the kernel etc. must still be running 'properly' and you can run tools to find out what is going on.
I'll see what I can do with my wife's machine... Should I need to run anything special on MY machine, or is it ready to accept remote terminal logins by default?
Check that you have sshd installed and running (I think it is by default) then simply ssh <machine IP or host-name> -l<username> You'll have to login as a normal user then su to root. Then you'll be able to look at top etc... Failing that, you simply try to ping the offending box - if it responds then there must be /something/ alive in there! <SNIP>
You can try ctrl-alt-f2 to see if a text console turns up...
When I say "no response to keyboard and mouse", I really do mean "no response to keyboard and mouse". :-)
Fair enough, thought you might say that.
Because I'm not *always* working, and because I have the password-protected screensaver on a 4-minute cycle,
Is there any reason why you can't extend that for a while, or even disable the ss for a few days?
*most* of the failures have occurred while the machine was relatively idle. It's possible that timed events may have been running when some failures happened, but mostly, there'd be two or three programs open but not performing any activity... only the screensaver would be actively using CPU cycles.
Now you mention timed events... Take a look at what cron and at are doing (check the man pages for the config file details.)
About half the time, a second KDE session (my wife) was also running at idle.
This has caused some strange effects here occasionally, but not a hard lockup.
However enough crashes have happened with only the one session running, that I doubt it's an issue.
There was no complaint from YaST when I installed 8.1, and no problem from SaX2 on the two or three occasions that I've run it. I've run YOU several times, so things should be as up-to-date as SuSE makes them.
I'm trying to set up Balsa, in GNOME, so that I can work -- including e-mail -- without invoking any KDE underpinnings (i.e., not using KMail that calls qt and a bunch of other stuff), but now I have to figure out fetchmail and sendmail, since Balsa doesn't appear to do the fetching and sending from my ISP mail account, all by itself as KMail did. If I get that going, and the crashes cease, then I'll have a good indication that there's a K problem.
Indeed, but remember to change the login and display manager to gdm from kdm, or you'll be using KDE 'underpinnings' anyway
I initially chose KDE3 because it was supposedly more thoroughly integrated by SuSE.
It is, but that doesn't necessarily make it a Good Thing...
/kevin
-- "Sweet moderation Heart of this nation Desert us not We are between the wars" Billy Bragg