On Tuesday 21 October 2008, Jamie Lokier wrote: > Btw, in most cases exit() should not be called in a *fork* child > either, let alone *vfork*. It will flush stdio buffers - and they may > get flushed by the parent when it exits too. Same for atexit() > handlers. > > Often if there's an exit() in a fork child and the parent too, one of > them should be _exit(), and it's usually the child.
that's really up to the developer to decide. some people want atexit() handlers processed, some dont. that's why i only ever touch _exit() for vfork() -- i'm not the original dev and i have no idea their intentions. especially a huge project like e2fsprogs. -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ 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
