[KDE/Mac] Cross-platform with kdeinit5, klauncher5, kded5 and friends
Brandon Allbery
allbery.b at gmail.com
Wed Feb 11 15:34:22 PST 2015
On Wed, Feb 11, 2015 at 6:31 PM, René J.V. <rjvbertin at gmail.com> wrote:
> I take that to mean that doing fork() doesn't oblige you to do an exec()
> afterwards, it's that you cannot do a fork() from a process that's not been
> started through exec.
I will guess that this is related to the fact that such processes are
actually started by launchd, and must play by launchd's rules (including
not using fork()) so launchd can keep track of them. This would also imply
that fork() is actually acceptable as long as the forked processes don't
try to use the UI, but are merely background worker processes that
communicate with the foreground process if they need UI interaction or etc.
--
brandon s allbery kf8nh sine nomine associates
allbery.b at gmail.com ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150211/528ad44a/attachment.html>
More information about the macports-dev
mailing list