[BusyBox] ctrl-c exits kills init:getty
Brian T.
btuch at usa.net
Fri Apr 25 12:53:04 UTC 2003
> >
> > 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
>
One other thing also, ctrl-c seems not to exit ping, tail, or other programs
that allow it. The console (ttyS0) doesn't lock (I can still hit <cr> and
get a line feed) but cannot get out of it. Can still telnet to the box
though.
-Brian
More information about the busybox
mailing list