regaining crashed consoles

regaining crashed consoles

[Gregory Nowak]

Hi all,

Sometimes when I telnet into a system over dial-up, the modem and sesion disconnects.
What I do then, is the 3 finger solute.
What is the best way to regain a crashed console like that?
Greg

Re: regaining crashed consoles

[Kirk Reiser]

This is the windows mentality personified.  You almost never have to
reboot your computer.  If you are in telnet and it crashes you can
usually get out of it by doing a control-] which will give you a
telnet> prompt.  Once there you can type quit to exit.  If for some
reason you cannot get the telnet prompt, you can change to another
console and type killall telnet, or whatever the program is named that
you are running.

If your console gets into a fucked up state, that is garbage
characters for your prompt. You can type reset to reset the console
and then stty sane to get your standard options back.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: regaining crashed consoles

[Kirk Wood]

On Tue, 11 Sep 2001, Gregory Nowak wrote:
> Sometimes when I telnet into a system over dial-up, the modem and sesion disconnects.
> What I do then, is the 3 finger solute.
> What is the best way to regain a crashed console like that?

I think a much better method would be to switch consoles. Then you can run
"ps aux" and kill off the bash process that coresponds to the telnet
session. If you wanted to kill the whole session, kill off the bash
process that coresponds. If you guess wrong, you of course kill off
another console. But all should regenterate nicely.

=======
Kirk Wood
Cpt.Kirk@1tree.net

The mind is like a parachute; it works much better when open.
If you're too open minded, your brains will fall out.

Re: regaining crashed consoles

[Jim Ruby]

I think something like this would work:

ps -t tty# where "#" is the concel your crashed in, this would give you a list of jobs in that concel, then use kill job number and its done.
On Tue, 11 Sep 2001 17:15:26 -0500 (CDT), Kirk Wood wrote:

>On Tue, 11 Sep 2001, Gregory Nowak wrote:
>> Sometimes when I telnet into a system over dial-up, the modem and sesion disconnects.
>> What I do then, is the 3 finger solute.
>> What is the best way to regain a crashed console like that?
>
>I think a much better method would be to switch consoles. Then you can run
>"ps aux" and kill off the bash process that coresponds to the telnet
>session. If you wanted to kill the whole session, kill off the bash
>process that coresponds. If you guess wrong, you of course kill off
>another console. But all should regenterate nicely.
>
>=======
>Kirk Wood
>Cpt.Kirk@1tree.net
>
>The mind is like a parachute; it works much better when open.
>If you're too open minded, your brains will fall out.
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: regaining crashed consoles

[Shaun Oliver]

ok, in that case, what the hell do you do when your keyboard won't
responde to anything.
I had this happen the other night and the only way I could get out of it
was the reset button.
ctrl+alt+del wouldn't even work. oh well, it's probably bound to happen
once in a blue moon right?



Shaun..

Cat, n.:
	Lapwarmer with built-in buzzer.

Email: shauno@goanna.net.au

On 11 Sep 2001, Kirk Reiser wrote:

> This is the windows mentality personified.  You almost never have to
> reboot your computer.  If you are in telnet and it crashes you can
> usually get out of it by doing a control-] which will give you a
> telnet> prompt.  Once there you can type quit to exit.  If for some
> reason you cannot get the telnet prompt, you can change to another
> console and type killall telnet, or whatever the program is named that
> you are running.
> 
> If your console gets into a fucked up state, that is garbage
> characters for your prompt. You can type reset to reset the console
> and then stty sane to get your standard options back.
> 
>   Kirk
> 
> -- 
> 
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: regaining crashed consoles

[Shaun Oliver]

I agree. I ain't had windows lock up for at least a month. and if I have,
it's usually been my own doing because I've tried to get too much out of
it.
you just gotta remember, you can't push windows too hard. it's not robust
enough.



Shaun..

Cat, n.:
	Lapwarmer with built-in buzzer.

Email: shauno@goanna.net.au

On Wed, 12 Sep 2001, Kirk Wood wrote:

> On Wed, 12 Sep 2001, Shaun Oliver wrote:
> > ok, in that case, what the hell do you do when your keyboard won't
> > responde to anything.
> 
> This shouldn't happen often. And unfortunately, there has been no
> foolproof means of recovery. If this happens regularly, something is major
> wrong with your system. And that goes for all regardless of system. I
> cringe when people say that it is normal for winblows to lock. It is not
> normal. While it is very true that winblows is not nearly as stable, and
> it is true that (most versions) require regular restarting to regain lost
> resources, it shouldn't regularly lock.
> 
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
> 
> The mind is like a parachute; it works much better when open.
> If you're too open minded, your brains will fall out.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: regaining crashed consoles

[Kirk Wood]

On Wed, 12 Sep 2001, Shaun Oliver wrote:
> ok, in that case, what the hell do you do when your keyboard won't
> responde to anything.

This shouldn't happen often. And unfortunately, there has been no
foolproof means of recovery. If this happens regularly, something is major
wrong with your system. And that goes for all regardless of system. I
cringe when people say that it is normal for winblows to lock. It is not
normal. While it is very true that winblows is not nearly as stable, and
it is true that (most versions) require regular restarting to regain lost
resources, it shouldn't regularly lock.

=======
Kirk Wood
Cpt.Kirk@1tree.net

The mind is like a parachute; it works much better when open.
If you're too open minded, your brains will fall out.