The process created by vfork() needs to _exit() instead of showing a potential error since it is an undefined behavior. So are calling the functions before execlp(). From 'man vfork()': "Standard description (From POSIX.1) The vfork() function has the same effect as fork(2), except that the behavior is undefined if the process created by vfork() either modifies any data other than a variable of type pid_t used to store the return value from vfork(), or returns from the function in which vfork() was called, or calls any other function before successfully calling _exit(2) or one of the exec(3) family of functions. " TBH it might be better to use a fork() or posix_spawn(). I recognized this by processes becoming zombies (and after some seconds they were reaped). //M Sent from my BlackBerry — the most secure mobile device |
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
