Michael Schnell wrote: > BTW.: AFAIK, clone() called with the appropriate arguments performs the > same action as fork() or vfork(). Thus, does fork() or vfork() just call > clone() ? Is the behavior of clone() (e.g. if or if not stall the parent > process until the child does *exec() or exit ) well defined or is it > depending on the arch (MMU or MMU-less) ?
clone() is dependent on the arch in lots of ways. vfork() doesn't just call clone(), because the way the child and parent process share the same stack complicates it. To daemonize, you don't use the same flags as you would to emulate fork() and vfork(), and have to use a little arch-specific assembler. -- Jamie _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
