On Thu, 9 Aug 2001, David Christensen wrote:
> Jay,
>
> I've tried this already, but the earliest I can run the command is in the
> .bash_profile script (and all of the scripts called init). By then it is
> already too late as 1 or more CTRL-C characters have been processed before
> bash gets to that command. I finally had to modify the init source code so
> that every terminal session it starts has "intr" as undefined.
This, I would say, is the proper solution. I think you could even rename
init to, say init.real, then create a shell script called init that runs
the stty command, then execs init.real.
--Jeremy
>
> David Christensen
>
> > > >
> > > > Question for the group: what mechanism is it that maps the
> > > > keypress CTRL-C
> > > > to SIGINT? Is it the TTY handler, or is it the
> > controlling process
> > > > (usually the shell)? Or something else?
> > >
> >
> >
> > "stty intr undef" will disable CTRL-C for the TTY.
Jeremy Impson
Sr. Associate Network Engineer
Advanced Technologies Department
Lockheed Martin Systems Integration
email: [EMAIL PROTECTED]
phone: 607-751-5618
fax: 607-751-6025
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
