Hi,
I recommend you to change your test system.
For example, you can modify /etc/systemd/system.conf and change DefaultTasksMax
there. But that is for the systemd started units...
Note that TasksMax these days can accept % values of kernel configured max
tasks too, meaning i.e. one can set it to 100%..... The upstream default is 15%
and we reverted that, meaning setting it to unlimited.
However something odd is going on.
I wonder if you are actually hitting UserTasksMax instead (which appears
to be under-documented).
I wonder if setting UserTasksMax=1000000 in /etc/systemd/logind.conf in
the [Login] section, restarting systemd-logind, creating a brand new
user session (logout _all_ sessions, and relogin) would actually solve
your problem?
ps. Also you can use a "drop-in" instead of modifying a config file, as all
config files in systemd support .d `drop-ins` like so:
instead of modifying /etc/systemd/system.conf one can instead install
files like these:
/{lib,etc,run}/systemd/system.conf.d/bump-tasks-max.conf
with like contents of
[Manager]
DefaultTasksMax=1000000
Depending on whether you want it to be packaged in a package, be a
config file, or be a runtime adjustment.
** Tags added: cosmic
** No longer affects: systemd (Ubuntu Cosmic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgstress03 fails because systemd limits number of
processes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
