From 3676d3f21f0e1e2e59cd2fcafc64acccd3782ef9 Mon Sep 17 00:00:00 2001 From: Simon Ruderich Date: Sat, 15 Nov 2014 18:35:05 +0100 Subject: [PATCH] vfork(): fix incorrect comment --- src/coloredstderr.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/src/coloredstderr.c b/src/coloredstderr.c index 064383e..fd83b15 100644 --- a/src/coloredstderr.c +++ b/src/coloredstderr.c @@ -534,11 +534,12 @@ pid_t vfork(void) { * isn't allowed to perform any memory-modifications before the exec() * (except the pid_t result variable of vfork()). * - * As some programs don't adhere to the standard (e.g. the "child" closes - * or dups a descriptor before the exec()) and this breaks our tracking of - * file descriptors (e.g. it gets closed in the parent as well), we just - * fork() instead. This is in compliance with the POSIX standard and as - * most systems use copy-on-write anyway not a performance issue. */ + * As we have to store changes to the file descriptors in memory (e.g. the + * "child" closes or dups a descriptor before the exec()) and this + * modifies the parent as well due to the semantics of vfork() - thus + * breaking the requirements of vfork(), we just use fork instead(). This + * is in compliance with the POSIX standard and as most systems use + * copy-on-write anyway not a performance issue. */ return fork(); } #endif -- 2.43.2