Alexey Toptygin wrote:
Why not have the tool create a monitor interface, open it, and fork;
the child drops privileges and does the reading, and the parent
wait(2)s for the child and removes the interface once it has collected
the child?
Good point, that'll work. Then again, I want this to run on really tiny
architectures and I'm thinking some of them might not have fork(), just
vfork(). Hmm.
johannes
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
