From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gopi@india.tejasnetworks.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: why is tty->pgrp set to -1 for console?
Date: Thu, 31 Jan 2002 12:09:22 -0500 [thread overview]
Message-ID: <20020131120922.A6447@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0201312050570.1490-100000@tn100build.india.tejasnetworks.com>
On Thu, Jan 31, 2002 at 08:58:58PM +0000, gopi@india.tejasnetworks.com wrote:
>
> hi..
>
> We had a problem that ctrl-c was not working on the console. I
> figured out that, ctrl-c was getting recognized as the 'intr' signal,
> but the function isig (in drivers/char/n_tty.c) sends a signal only if
> the tty->pgrp > 0.
>
> I have put a print stmt in this function and checked that the value
> is 'tty->pgrp = ffffffff' (which is -1).
>
> What is the correct procedure to follow to get around this problem
> and get ctrl-c working on console?
You need to run a getty on the console in order for SIGINT to get sent
properly. That should be all it takes. If the pgrp hasn't been set
yet, the kernel doesn't know where to send them.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-31 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 12:14 kernel hang when machine_restart called from isr gopi
2002-01-31 20:58 ` why is tty->pgrp set to -1 for console? gopi
2002-01-31 17:09 ` Daniel Jacobowitz [this message]
2002-01-31 21:34 ` Scott Anderson
2002-02-01 19:12 ` gopi
2002-02-21 0:53 ` Unable to write to SIMASK gopi
2002-02-20 21:27 ` Ricardo Scop
2002-02-21 17:34 ` gopi
-- strict thread matches above, loose matches on Subject: below --
2002-01-31 19:14 why is tty->pgrp set to -1 for console? David Boutcher
2002-01-31 20:49 ` mod+linuxppc-dev
2002-01-31 20:53 ` Dan Malek
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=20020131120922.A6447@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=gopi@india.tejasnetworks.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.