Leo Famulari skribis:
> On Tue, Apr 19, 2016 at 05:57:05PM +0200, Ludovic Courtès wrote:
>> What about this:
>>
>
>> diff --git a/etc/guix-daemon.service.in b/etc/guix-daemon.service.in
>> index 28ef000..c79f867 100644
>> --- a/etc/guix-daemon.service.in
>> +++ b/etc/guix-daemon.service.in
>> @@
On Tue, Apr 19, 2016 at 05:57:05PM +0200, Ludovic Courtès wrote:
> What about this:
>
> diff --git a/etc/guix-daemon.service.in b/etc/guix-daemon.service.in
> index 28ef000..c79f867 100644
> --- a/etc/guix-daemon.service.in
> +++ b/etc/guix-daemon.service.in
> @@ -10,6 +10,7 @@ ExecStart=@bindir@
Joram Schrijver skribis:
> Heh, no I'm not. I have to do it with 4 cores + hyperthreading. My first
> `guix pull` did have to build many things though, spawning numerous
> threads in some cases. I eye-sampled the thread counts during one try
> and they were certainly in the hundreds.
Oh, then it
Heh, no I'm not. I have to do it with 4 cores + hyperthreading. My first
`guix pull` did have to build many things though, spawning numerous
threads in some cases. I eye-sampled the thread counts during one try
and they were certainly in the hundreds.
I installed Guix from the AUR[1], so I was run
On Sun, Apr 17, 2016 at 12:46:16AM +0200, Ludovic Courtès wrote:
> Leo Famulari skribis:
>
> > On Sat, Apr 16, 2016 at 03:12:15PM +0200, Joram Schrijver wrote:
> >> I am running Arch Linux, also with systemd 229. It doesn't look like
> >> Debian applies any patches to systemd, so our installation
Leo Famulari skribis:
> On Sat, Apr 16, 2016 at 03:12:15PM +0200, Joram Schrijver wrote:
>> I am running Arch Linux, also with systemd 229. It doesn't look like
>> Debian applies any patches to systemd, so our installations should
>> pretty much be the same.
>>
>> Perhaps the limit is only reach
On Sat, Apr 16, 2016 at 03:12:15PM +0200, Joram Schrijver wrote:
> I am running Arch Linux, also with systemd 229. It doesn't look like
> Debian applies any patches to systemd, so our installations should
> pretty much be the same.
>
> Perhaps the limit is only reached during the build process of
On Sat, Apr 16, 2016, at 03:29 AM, Leo Famulari wrote:
> On Fri, Apr 15, 2016 at 01:37:32AM +0200, Joram Schrijver wrote:
> > Hi,
> >
> > In version 228, systemd introduced a unit attribute `TasksMax`[1] that
> > limits the number of tasks that can run in a unit. It has effect on
> > kernel versio
On Fri, Apr 15, 2016 at 01:37:32AM +0200, Joram Schrijver wrote:
> Hi,
>
> In version 228, systemd introduced a unit attribute `TasksMax`[1] that
> limits the number of tasks that can run in a unit. It has effect on
> kernel versions 4.3 and up, kernel threads and userspace process count
> towards
On Fri, Apr 15, 2016 at 01:37:32AM +0200, Joram Schrijver wrote:
> Hi,
>
> In version 228, systemd introduced a unit attribute `TasksMax`[1] that
> limits the number of tasks that can run in a unit. It has effect on
> kernel versions 4.3 and up, kernel threads and userspace process count
> towards
Hi,
In version 228, systemd introduced a unit attribute `TasksMax`[1] that
limits the number of tasks that can run in a unit. It has effect on
kernel versions 4.3 and up, kernel threads and userspace process count
towards the limit, and the default value is 512.
Running `guix pull` without changi
11 matches
Mail list logo
