summaryrefslogtreecommitdiff
path: root/buckets/allocator.c
diff options
context:
space:
mode:
authorLorry Tar Creator <lorry-tar-importer@lorry>2013-06-03 18:34:10 +0000
committerLorry Tar Creator <lorry-tar-importer@lorry>2013-06-03 18:34:10 +0000
commitf143c3cab79c59dd57124f19d16ac35253843136 (patch)
tree9fa67aa3d59e9d96f5f37858e95c4ab91960ea92 /buckets/allocator.c
parent6f61a1acd01dc2ad1d2f5c1f7458702c77c69f9c (diff)
downloadlibserf-tarball-master.tar.gz
Diffstat (limited to 'buckets/allocator.c')
-rw-r--r--buckets/allocator.c14
1 files changed, 7 insertions, 7 deletions
diff --git a/buckets/allocator.c b/buckets/allocator.c
index 857cc74..108167e 100644
--- a/buckets/allocator.c
+++ b/buckets/allocator.c
@@ -144,14 +144,14 @@ serf_bucket_alloc_t *serf_bucket_allocator_create(
}
#endif
- /* ### this implies buckets cannot cross a fork/exec. desirable?
- *
- * ### hmm. it probably also means that buckets cannot be AROUND
- * ### during a fork/exec. the new process will try to clean them
- * ### up and figure out there are unfreed blocks...
- */
+ /* NOTE: On a fork/exec, the child won't bother cleaning up memory.
+ This is just fine... the memory will go away at exec.
+
+ NOTE: If the child will NOT perform an exec, then the parent or
+ the child will need to decide who to clean up any
+ outstanding connection/buckets (as appropriate). */
apr_pool_cleanup_register(pool, allocator,
- allocator_cleanup, allocator_cleanup);
+ allocator_cleanup, apr_pool_cleanup_null);
return allocator;
}