[BusyBox] nc problem still stumps me

[Tom Oehser]

Well, I looked at the strace and the source for the original nc and
the busybox nc, and I don't see anything obvious why the busybox nc
doesn't work the same way.  If I have something like:

while [ true ] ; do nc -l -p 11111 -e /bin/true ; done

and repeatedly connect to it, the real nc will continue to work every
time, but the busybox nc will work once and then fail saying that the
port is already in use and it can't bind.  What I don't understand is
that it seems to be the condition busybox *leaves* it in that is bad,
not the way it initializes it- that is, after the busybox one runs,
the real nc can't bind it, either.

But, what confuses me is that nc just hands the file descriptor off
to an execed process- so nc should have *nothing* to do with how it
is handled when that process ends.  There must be some flag or socket
option or setup that affects the socket itself?

I'll keep at it, but I'm open to ideas...

-Tom