mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bill J.Xu" <xujz@neusoft.com>
To: Edgar Toernig <froese@gmx.de>,
	root@chaos.analogic.com, rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: "ctrl+c" disabled!
Date: Mon, 01 Sep 2003 12:50:25 +0800	[thread overview]
Message-ID: <002101c37044$8f49eea0$2a01010a@avwindows> (raw)
In-Reply-To: <3F4618FF.BDC97C99@gmx.de>

Thanks all of you for helping me to resole the problem of "ctrl+c disable".

and now, the problem has been resolved.At the very start,when the system start,it give the user a shell prompt directly,at this instance,the "ctrl+c" disable. Afterward,I change the file of "/etc/inittab" as this:"s1:12345:respawn:/sbin/agetty 9600 ttyS0 vt100",then the problem is resolved.Maybe this is a apish a mistake.
:-)

thanks

Bill

----- Original Message ----- 
From: "Edgar Toernig" <froese@gmx.de>
To: "Bill J.Xu" <xujz@neusoft.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, August 22, 2003 9:22 PM
Subject: Re: "ctrl+c" disabled!


> "Bill J.Xu" wrote:
> > 
> > after run od -tx1, the following is the result
> > ------------------------------------------------
> > bash-2.05# ./od -tx1
> > 0000000
> > ------------------------------------------------
> 
> Either terminal sends nothing or line-discipline caught ^C correctly
> but sent signal to wrong process or process ignores sigint.
> 
> > and I use "killall xxx_appname" to kill the progress after telnet the linux box.
> 
> Check whether "killall -INT xxx_appname" is able to kill the process.
> 
> Try killing the process via Ctrl-Z and then "kill %%".
> 
> Ciao, ET.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

      reply	other threads:[~2003-09-01  7:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21 12:30 Bill J.Xu
2003-08-21 12:46 ` Richard B. Johnson
2003-08-22  1:50   ` Bill J.Xu
2003-08-22 13:16     ` Richard B. Johnson
2003-08-22  2:04 ` Edgar Toernig
2003-08-22  2:12   ` Bill J.Xu
2003-08-22  2:42     ` Edgar Toernig
2003-08-22  3:22       ` Bill J.Xu
2003-08-22  4:14         ` Charles Lepple
2003-08-22  4:55           ` Bill J.Xu
2003-08-22 11:27             ` Russell King
2003-08-22 13:22         ` Edgar Toernig
2003-09-01  4:50           ` Bill J.Xu [this message]

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='002101c37044$8f49eea0$2a01010a@avwindows' \
    --to=xujz@neusoft.com \
    --cc=froese@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=root@chaos.analogic.com \
    /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

Powered by JetHome