Re: Avoiding threads in the daemon

2014-12-26 Thread Ludovic Courtès
Eelco Dolstra skribis: > On 19/12/14 19:20, Eelco Dolstra wrote: > >> I see a few ways to get PID namespaces back: >> >> * Do a regular fork followed by clone(... | CLONE_NEWPID | CLONE_PARENT) >> (after >> which the intermediate process can exit). > > This has been implemented in bd0f362d2fad1

Re: Avoiding threads in the daemon

2014-12-23 Thread Eelco Dolstra
Hi, On 19/12/14 19:20, Eelco Dolstra wrote: > I see a few ways to get PID namespaces back: > > * Do a regular fork followed by clone(... | CLONE_NEWPID | CLONE_PARENT) > (after > which the intermediate process can exit). This has been implemented in bd0f362d2fad1dd5f28e762011888b5eabd21280. -

Re: Avoiding threads in the daemon

2014-12-19 Thread Ludovic Courtès
Hi, Eelco Dolstra skribis: > On 18/12/14 17:32, Ludovic Courtès wrote: > >> Thus, I think Nix commit 49fe95 (which introduces monitor-fd.hh, which >> uses std::thread just for convenience) should be reverted, along with >> the subsequent commits to that file; then commit 524f89 can be reverted.

Re: Avoiding threads in the daemon

2014-12-19 Thread Eelco Dolstra
Hi, On 18/12/14 17:32, Ludovic Courtès wrote: > Thus, I think Nix commit 49fe95 (which introduces monitor-fd.hh, which > uses std::thread just for convenience) should be reverted, along with > the subsequent commits to that file; then commit 524f89 can be reverted. I really don't want to get rid