2009/6/3 Mike Frysinger <[email protected]> > On Tuesday 02 June 2009 19:39:54 wilbur.chan wrote: > > 2009/6/3, Mike Frysinger <[email protected]>: > > > On Tuesday 02 June 2009 10:53:27 wilbur.chan wrote: > > >> busybox 1.13.1 , msh > > >> > > >> I wrote a procedure of infinite loop. When I pressed ctrl+c , this > > >> procedure was killed by SIGINT, however, the msh seemed to be killed > > >> too( and busybox respawn a new msh). > > > > > > known issue, msh sucks. use hush. > > > > > >> could someone tell me why? > > > > > > there's a race condition in the code due to the use of vfork. not > worth > > > fixing. > > > > When ctrl+C pressed , SIGINT will be send to both msh and our > > application (they are of the same group), and what happened next? > > a different bug, and yet another example of msh sucking. it would require > a > bit of effort to fix. > > > I looked up the code of vfork in kernel 2.6.21.7 , but can't find > > where the condition is . > > the problem is in msh, not the kernel. > > the answer is still the same: msh isnt supported, use hush. > -mike >
Thank you very much, but I really have to solve this problem,because we have some products using msh. well,could you please give me some links refer to this bug? (vfork) regards
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
