From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: regaining crashed consoles
Date: Tue, 11 Sep 2001 17:15:26 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0109111713010.13702-100000@ignatious> (raw)
In-Reply-To: <20010911152209.A279@linserver.megsinet.net>
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.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Kirk Reiser
` Shaun Oliver
` Kirk Wood
` Shaun Oliver
` Kirk Wood [this message]
` Jim Ruby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0109111713010.13702-100000@ignatious \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).