luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-04-19 21:59:17 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add a note on restrictions of child setup functions

Browse Source 
svn path=/trunk/; revision=6208
This commit is contained in:
Matthias Clasen 2007-12-29 05:18:58 +00:00
parent 35f3f588ae
commit fd28036701
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/reference/ChangeLog
View File

@ -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> 2007-12-24 Benjamin Otte <otte@gnome.org>
* glib/tmpl/timers.sgml: Add a warning about g_thread_init * glib/tmpl/timers.sgml: Add a warning about g_thread_init

6
docs/reference/glib/tmpl/spawn.sgml
View File

@ -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. function will thus only affect the child, not the parent.
</para> </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> <para>
On Windows the function is called in the parent. Its usefulness on On Windows the function is called in the parent. Its usefulness on
Windows is thus questionable. In many cases executing the child setup Windows is thus questionable. In many cases executing the child setup