When I interrupt (^C) a looping process (ping, tail -f, or a script with a while or for loop in it), very strange things happen, including ...
* a phantom sh process is created which has my shell process as its parent * the next command line goes "nowhere" * command history is partly deleted, and CWD may change to an earlier one * if the killed script reads from STDIO, it may grab some of my command lines. * STTY settings may be erratic -- e.g. no more newlines * sometimes zombies result. Attempts to kill these processes may succeed, for some, but one always remains, and each time it is killed, it reappears as a new process, with the killing shell as its parent. If these loops are run in the BG, they can be killed ok. I can provide transcripts if necessary, but I thought I'd start by asking if this is a known condition, perhaps caused by inconsistent busybox shell feature configuration? (No job control) Thanks, -- Peter Renzland BusyBox v1.12.2 & BusyBox v1.12.3 Linux 2.4.20 on mips (WRT54GL router) running Tomato _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
