On Fri, 20 Feb 2015 22:29:04 +0000, Ola Fosheim Grøstad wrote:

> This robust philosophy somehow got lost in the quest for bleeding edge.

i still missing it. sure, we can write our code in this style today, but with all that libraries that can create threads without you knowing about it (heh, have you ever used `getaddrinfo_a(GAI_NOWAIT)`? a hideous "solution"!)...

On 02/18/2015 09:27 PM, Byron Heads wrote:
> I have a medium size daemon application that uses several threads, libasync, and daemonize.  On windows it runs correctly with GC enabled, but on linux the GC causes a deadlock while allocating memory.

Have you been able to resolve the issue?
There were a number of suggestions in the thread, but we never heard
back from you.
Meanwhile the author of daemonized came up with another idea, using
exec instead of fork.
https://github.com/NCrashed/daemonize/issues/2

On Sat, 28 Feb 2015 06:09:16 +0100, Martin Nowak wrote:

> Meanwhile the author of daemonized came up with another idea, using exec instead of fork. https://github.com/NCrashed/daemonize/issues/2

ahem. http://forum.dlang.org/post/mc35ap$2dvo$51@digitalmars.com

On Saturday, 28 February 2015 at 05:32:51 UTC, ketmar wrote:
> On Sat, 28 Feb 2015 06:09:16 +0100, Martin Nowak wrote:
>
>> Meanwhile the author of daemonized came up with another idea, using exec
>> instead of fork. https://github.com/NCrashed/daemonize/issues/2
>
> ahem. http://forum.dlang.org/post/mc35ap$2dvo$51@digitalmars.com

Bug 6846 is supposedly caused by usage of GC. Can't recent spawnProcess from phobos be used to start a process? It works around GC after fork sufficiently enough.

On Mon, 02 Mar 2015 08:15:12 +0000, Kagamin wrote:

> On Saturday, 28 February 2015 at 05:32:51 UTC, ketmar wrote:
>> On Sat, 28 Feb 2015 06:09:16 +0100, Martin Nowak wrote:
>>
>>> Meanwhile the author of daemonized came up with another idea, using exec instead of fork. https://github.com/NCrashed/daemonize/issues/2
>>
>> ahem. http://forum.dlang.org/post/mc35ap$2dvo$51@digitalmars.com
> 
> Bug 6846 is supposedly caused by usage of GC. Can't recent spawnProcess from phobos be used to start a process? It works around GC after fork sufficiently enough.

it doesn't "workaround" in any way, it does exactly what it is supposed to do: it running *new* process. no workarounds needed for that, and it does no allocations in child process after forking point.

I mean, if it used GC after fork, like in bug 6846, that would be untidy (it's complicated because GC is always a temptation).