From: Joram Schrijver <i+guix-devel@joram.io>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: guix-daemon hitting systemd TasksMax
Date: Sat, 16 Apr 2016 15:12:15 +0200 [thread overview]
Message-ID: <1460812335.1088225.580600441.5A60AF4E@webmail.messagingengine.com> (raw)
In-Reply-To: <20160416012901.GB12389@jasmine>
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 versions 4.3 and up, kernel threads and userspace process count
> > towards the limit, and the default value is 512.
> >
> > Running `guix pull` without changing any settings crashed for me,
> > because building/testing texinfo hit this task limit. Increasing it to
> > 1024 using `systemctl set-property guix-daemon.service TasksMax=1024`
> > fixed the problem.
>
> Interesting. What operating system are you using? I'm running systemd
> 229 on Debian testing and I don't have this issue, nor have I altered
> this setting.
>
> It would be useful to know what the difference is between our systemd
> installations. I don't see anything related to TasksMax in
> systemd-229's NEWS:
>
> https://github.com/systemd/systemd/blob/master/NEWS
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 some
specific packages?
--
Joram
next prev parent reply other threads:[~2016-04-16 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 23:37 guix-daemon hitting systemd TasksMax Joram Schrijver
2016-04-15 14:35 ` Efraim Flashner
2016-04-16 1:29 ` Leo Famulari
2016-04-16 13:12 ` Joram Schrijver [this message]
2016-04-16 16:14 ` Leo Famulari
2016-04-16 22:46 ` Ludovic Courtès
2016-04-18 20:33 ` Leo Famulari
2016-04-18 20:42 ` Joram Schrijver
2016-04-19 15:57 ` Ludovic Courtès
2016-04-20 1:20 ` Leo Famulari
2016-04-25 21:37 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1460812335.1088225.580600441.5A60AF4E@webmail.messagingengine.com \
--to=i+guix-devel@joram.io \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).