On Fri, May 06, 2016 at 06:42:53PM -0500, Martin Pitt wrote:
> Hello all,
>
> Sebastian Schmidt [2016-05-05 20:14 +0200]:
> > Whilst debugging why Chrome would regularly fail to create new
> > threads[1] and zsh couldn’t fork I noticed that:
> > - - All affected processes run in the /system.slice/
On Sat, May 7, 2016 at 1:25 PM, Santiago Vila wrote:
> I'm using a hand-made autobuilder which is triggered by cron, asks a
> server for a package to build and uses sbuild to build the package.
> Should I override this for the cron service only?
cron probably shouldn't be running the actual jobs
affects 823530 ruby2.3
affects 823530 openexr
thanks
On Fri, 6 May 2016, Antonio Terceiro wrote:
> Will every package need to start declaring higher limits explicitly?
I also would like to know the answer for that question.
How does a package which needs a higher limit to build is supposed to
o
Hello all,
Sebastian Schmidt [2016-05-05 20:14 +0200]:
> Whilst debugging why Chrome would regularly fail to create new
> threads[1] and zsh couldn’t fork I noticed that:
> - - All affected processes run in the /system.slice/xdm.service cgroup
> - - “systemctl status xdm.service” says “Tasks: 476
Control: severity -1 important
On Thu, 05 May 2016 20:14:20 +0200 Sebastian Schmidt wrote:
> Package: systemd
> Version: 229-3
> Severity: normal
> Tags: upstream
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> Whilst debugging why Chrome would regularly fail to create new
>
Package: systemd
Version: 229-3
Severity: normal
Tags: upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Whilst debugging why Chrome would regularly fail to create new
threads[1] and zsh couldn’t fork I noticed that:
- - All affected processes run in the /system.slice/xdm.service cgro
6 matches
Mail list logo
