CTRL-C is actualy a signal 1. Check if stty -a says something like: stty -a speed 38400 baud; rows 24; columns 80; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; ....
2. do kill -2 <pid> so see if hush or something else eats signals re, wh Am 04.07.2011 15:11, schrieb Gilles: > On Mon, 04 Jul 2011 15:00:32 +0200, walter harms <[email protected]> > wrote: >> does the current version in GIT behave the same way ? > > I don't know. Busybox is built through Buildroot, so I never > cross-compiled it manually. > > Actually, it seems to be an issue with Hush, as CTRL+c doesn't work > either when running "iperf". > > Is there an option I should add/remove in the Busybox section? > ============= > Choose your default shell (hush) ---> > --- hush > [*] bash-compatible extensions > [ ] help builtin > [*] Interactive mode > [ ] Job control > [ ] Process substitution > [*] Support if/then/elif/else/fi > [*] Support for, while and until loops > [*] Support case ... esac statement > [ ] Support funcname() { commands; } syntax > [ ] Support export '-n' option > [ ] Pseudorandom generator and $RANDOM variable > [ ] lash (deprecated: aliased to hush) > [ ] msh (deprecated: please use hush) > [*] POSIX math support > [ ] Extend POSIX math support to 64 bit > [ ] Hide message on interactive shell startup > [ ] cttyhack > ============= > > FWIW, I work on the appliance through the SecureCRT terminal emulator > connected to the serial port. > > Thank you. > > _______________________________________________ > busybox mailing list > [email protected] > http://lists.busybox.net/mailman/listinfo/busybox > > _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
