[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [BusyBox] ctrl-c exits kills init:getty
From:       "Brian T." <btuch () usa ! net>
Date:       2003-04-28 17:12:24
[Download RAW message or body]





> On Thu Apr 24, 2003 at 05:44:00PM -0500, Brian T. wrote:
> > Hi,
> >
> > I recently upgraded our Embedded distro from Busybox 0.60.0 to 0.60.5.
Most
> > of the time now ctrl-c will kill getty when logged in through the
console,
> > and force users to log back in again.  I noticed that after upgrading,
when
> > the unit boots it prints out a "getty:" by itself on one line just
before
> > getting the /etc/issue login screen.  The older version of busybox
didn't do
> > this.  The unit will also print out "getty:" when ctrl-c is hit.  Has
anyone
> > else had this problem?  I ruled out that it is not Tinylogin (which is
> > getty) since I rolled back to Tinylogin 0.80.0 and I had the same
result.
> > (running BB 0.60.0 and Tinylogin 1.4 I don't have this problem).  I am
also
> > using the 2.4.20 kernel.  Anyone else seen this?
>
> When you say you are running on the console, are you really
> running on /dev/console?  What does your /etc/inittab file
> show?
>
>  -Erik

A couple other things I have noticed between 60.0 and 60.5 :

"killall -HUP init" doesn't seem to reread /etc/inittab anymore.

If I set my console to 115200 with the line

ttyS0::respawn:/bin/getty 115200 -

in inittab (I was running at 9600) and hit ctrl-c I get the output to the
screen:

getty(): TIOCSPGR

Does anyone know what this means?

-Brian







[prev in list] [next in list] [prev in thread] [next in thread]