From c873fc3fe785efe43f697295782b7613d7c5c021 Mon Sep 17 00:00:00 2001
From: Jean-Francois Dockes <jfd@recoll.org>
Date: Tue, 16 Jun 2015 09:38:41 +0200
Subject: [PATCH] doc

---
 website/idxthreads/forkingRecoll.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/website/idxthreads/forkingRecoll.txt b/website/idxthreads/forkingRecoll.txt
index 6c54885b..496d28c9 100644
--- a/website/idxthreads/forkingRecoll.txt
+++ b/website/idxthreads/forkingRecoll.txt
@@ -215,4 +215,8 @@ https://bugzilla.redhat.com/show_bug.cgi?id=193631
 Is Linux vfork thread-safe ? Quoting interesting comments from Solaris
 implementation: No answer to the issues cited though.
 https://sourceware.org/bugzilla/show_bug.cgi?id=378
+Aussi:
+http://blog.famzah.net/2009/11/20/fork-gets-slower-as-parent-process-use-more-memory/
+http://blog.famzah.net/2009/11/20/a-much-faster-popen-and-system-implementation-for-linux/
+Avec un workaround basé sur clone (donc linux-only). Tried it but crashes.
 ////