Avoiding forced shutdown from non-functioning system

[Bart Silverstrim]

Martin Laberge wrote:
> On June 4, 2007 12:36:29 Chris wrote:
>> Hello everybody...I'm about as new as you can be so please forgive my
>> ignorance.
>>
>> I have just put a test computer together to learn....and learn well
>> Ubuntu. (I'm coming from Open Suse...to many issues that never seemed to
>> get resolved.)  
>> For reference the pc uses the Intel 945G chipset (with onboard
>> graphics),512MB DDR2 RAM and a SATA HD.  
>> I'm assuming it's some drive conflict, but with this machine the machine
>> stops responding.  This last time it was the mouse would still function
>> but I couldn't click on anything, and the keys wouldn't function.  Other
>> times the nothing would function and the machine would just lock up.
>> Other than just dumping the power on the machine (or using the "Forced
>> Misbehaving"applet is there another way to view what the heck is going
>> on with this system?  
>> Also sometime when the machine boots the desktop would show, but the
>> panel would not show unless I click on the Desktop. Any idea why this
>> happens.
>> I haven't notice this issue with the Intels 865 or 875 chipsets...just
>> the 945...?
>>
>> Also guys I have some questions about things that may not be
>> techincal....where is the best place to ask questions like what's the
>> best software for remote desktop for Ubuntu to a WinXP machine...and
>> things like that?
>>
>> Thanks,
>> Chris
>>
>>
>>
> 
> for the best soft to remote access ANY OS, look at VNC (or it's derivate)
> it can remote access other machine screen and mouse and keyb,
> from/to linux,windows,os/x (once properly configured)
> and is easy to use from any platform

Only if you want to control the *console*...that is, the interface on 
the active system, not the text console.  For remote access I find SSH 
to be better.  Use it with -X to forward X sessions...I recently found 
it very handy for things like running Synaptic on a system that is 
downstairs from my current location.  The application appears on your 
desktop as if it were any ordinary application, but the actual 
processing and work is being done on the remote system.

I also use it when a machine acts up; if the interface is the only thing 
that is locked but the OS is still alive, I can ssh into it and look for 
the errant process and kill it, or if need be issue a sudo reboot.

VNC wouldn't work because it would be locked with the interface that is 
having the problem.