Re: a quick linux tip

Re: a quick linux tip

[Darragh]

Hello,
talking of things going wrong, does any one know how to pass the exit
command to another console?  it would be a handy thing to know about...

Darragh
----- Original Message -----
From: "Tyler Spivey" <tspivey8@telus.net>
To: <speakup@braille.uwo.ca>
Sent: Thursday, August 22, 2002 8:16 PM
Subject: a quick linux tip


> well, i decided to contribute my .02 to here, here goes:
> on most linux systems, maybe some other unix systems,
> there is a command called reset.
> if your terminal gets messed up (o echoing of commands, etc)
> or wierd things appear (hard to explain, but really odd things instead of
a shell prompt
> for example), you can type reset at a shell prompt.
> that usually fixes the problem if it's a terminal issue.
> i don't know if this hapens on the linux console, but it happens to me on
my serial terminal.
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: a quick linux tip

[Terry D. Cudney]

Hi Darragh,

	You don't "pass the exit" to another console.

	Rather, do a:

	kill -9 PID

	where PID is the Process ID of the console (usually 'bash') process that you want to cause to "exit". You obtain the PID from the 'ps ax' commmand which will list PID's and lots of other info about all the processes runn
ing in your system.

HTH,
	--terry

-- 

Name:	Terry D. Cudney
Phone:	(705) 422-0039
E-mail:	terry@CottageInWasaga.com
Web:	www.CottageInWasaga.com

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html

Having a smoking section in a restaurant is like...
having a peeing sectionin a swimming pool.

Re: a quick linux tip

[Darrell Shandrow]

Hi Darragh,

How about using the ps command to locate the process for that console, then
using kill to get rid of it?

----- Original Message -----
From: "Darragh" <darraghoheiligh@eircom.net>
To: <speakup@braille.uwo.ca>
Sent: Thursday, August 22, 2002 6:06 PM
Subject: Re: a quick linux tip


> Hello,
> talking of things going wrong, does any one know how to pass the exit
> command to another console?  it would be a handy thing to know about...
>
> Darragh
> ----- Original Message -----
> From: "Tyler Spivey" <tspivey8@telus.net>
> To: <speakup@braille.uwo.ca>
> Sent: Thursday, August 22, 2002 8:16 PM
> Subject: a quick linux tip
>
>
> > well, i decided to contribute my .02 to here, here goes:
> > on most linux systems, maybe some other unix systems,
> > there is a command called reset.
> > if your terminal gets messed up (o echoing of commands, etc)
> > or wierd things appear (hard to explain, but really odd things instead
of
> a shell prompt
> > for example), you can type reset at a shell prompt.
> > that usually fixes the problem if it's a terminal issue.
> > i don't know if this hapens on the linux console, but it happens to me
on
> my serial terminal.
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

a quick linux tip

[Tyler Spivey]

well, i decided to contribute my .02 to here, here goes:
on most linux systems, maybe some other unix systems,
there is a command called reset.
if your terminal gets messed up (o echoing of commands, etc)
or wierd things appear (hard to explain, but really odd things instead of a shell prompt
for example), you can type reset at a shell prompt.
that usually fixes the problem if it's a terminal issue.
i don't know if this hapens on the linux console, but it happens to me on my serial terminal.

Re: a quick linux tip

[Gregory Nowak]

After doing reset, I also type "stty sane" to restore things to how they should be.
Greg


On Thu, Aug 22, 2002 at 08:16:02PM +0000, Tyler Spivey wrote:
> well, i decided to contribute my .02 to here, here goes:
> on most linux systems, maybe some other unix systems,
> there is a command called reset.
> if your terminal gets messed up (o echoing of commands, etc)
> or wierd things appear (hard to explain, but really odd things instead of a shell prompt
> for example), you can type reset at a shell prompt.
> that usually fixes the problem if it's a terminal issue.
> i don't know if this hapens on the linux console, but it happens to me on my serial terminal.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: a quick linux tip

[Raul A. Gallegos]

Terry D. Cudney said the following on Thu, Aug 22, 2002 at 10:17:40PM -0400:
> 	You don't "pass the exit" to another console.
> 
> 	Rather, do a:
> 
> 	kill -9 PID


kill -1 also works.  I don't know all the implications of the kill
command and it's parameters however from what I've been told and what
I've seen, a -9 is usually the last resort of killing a process.  Some
can just take a plain sighup -1 in the case of a bash process it will
reset it and kill the console connection.  If you do a kill -1
pid_of_named it will re-read the named.conf configuration files like if
you add new zones.  If you want to kill a process that will not work
right with a -1 then -TERM -15 will do the trick.  And then if those
don't work I resort to a -9 to really force it to die.

Just my 2 cents worth.

-- 
Yesterday is history, tomorrow is a mystery, today is a gift.
Enjoy that gift, that's why it's called the present.
Raul A. Gallegos http://www.asmodean.net/contact.html

Re: a quick linux tip

[Gregory Nowak]

You don't want to use kill on named, use rndc instead.
Greg


On Fri, Aug 23, 2002 at 08:51:23AM -0500, Raul A. Gallegos wrote:
> Terry D. Cudney said the following on Thu, Aug 22, 2002 at 10:17:40PM -0400:
> > 	You don't "pass the exit" to another console.
> > 
> > 	Rather, do a:
> > 
> > 	kill -9 PID
> 
> 
> kill -1 also works.  I don't know all the implications of the kill
> command and it's parameters however from what I've been told and what
> I've seen, a -9 is usually the last resort of killing a process.  Some
> can just take a plain sighup -1 in the case of a bash process it will
> reset it and kill the console connection.  If you do a kill -1
> pid_of_named it will re-read the named.conf configuration files like if
> you add new zones.  If you want to kill a process that will not work
> right with a -1 then -TERM -15 will do the trick.  And then if those
> don't work I resort to a -9 to really force it to die.
> 
> Just my 2 cents worth.
> 
> -- 
> Yesterday is history, tomorrow is a mystery, today is a gift.
> Enjoy that gift, that's why it's called the present.
> Raul A. Gallegos http://www.asmodean.net/contact.html
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup