Add a note on restrictions of child setup functions

svn path=/trunk/; revision=6208

diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog
index 85f7b9eece32fda282bb429225b33a86ddff5ba3..a1c4d9021efb6e81ae8644cc25d1418d63efd4b1 100644 (file)
--- a/docs/reference/ChangeLog
+++ b/docs/reference/ChangeLog
@@ -1,3 +1,8 @@
+2007-12-29  Matthias Clasen  <mclasen@redhat.com>
+
+       * glib/tmpl/spawn.sgml: Add a warning about allowed functions
+       between fork() and exec().
+
 2007-12-24  Benjamin Otte  <otte@gnome.org>
 
        * glib/tmpl/timers.sgml: Add a warning about g_thread_init

diff --git a/docs/reference/glib/tmpl/spawn.sgml b/docs/reference/glib/tmpl/spawn.sgml
index f4d6ef0c99126d3c53651825ac6f9ab6e94bd43d..c744cee04313cab73ff5b978a4bb1072138f74a7 100644 (file)
--- a/docs/reference/glib/tmpl/spawn.sgml
+++ b/docs/reference/glib/tmpl/spawn.sgml
@@ -86,6 +86,12 @@ to perform but before calling exec(). On POSIX actions taken in this
 function will thus only affect the child, not the parent.
 </para>
 
+<para>
+Note that POSIX allows only async-signal-safe functions (see signal(7)) 
+to be called in the child between fork() and exec(), which drastically 
+limits the usefulness of child setup functions. 
+</para>
+
 <para>
 On Windows the function is called in the parent. Its usefulness on
 Windows is thus questionable. In many cases executing the child setup