[Bug 2048083] Re: [systemd-coredump] ProcessSizeMax setting does not seem to have any effect

Nick Rosbrook 2048083 at bugs.launchpad.net
Thu Jan 4 16:05:29 UTC 2024


I think the setting you are looking for is ExternalSizeMax=[1]. The
ProcessSizeMax=[2] seems to clarify this as well:

"The maximum size in bytes of a core which will be processed. Core dumps
exceeding this size may be stored, but the stack trace will not be
generated."

[1] https://www.freedesktop.org/software/systemd/man/latest/coredump.conf.html#ExternalSizeMax=
[2] https://www.freedesktop.org/software/systemd/man/latest/coredump.conf.html#ProcessSizeMax=

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2048083

Title:
  [systemd-coredump] ProcessSizeMax setting does not seem to have any
  effect

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The systemd-coredump ProcessSizeMax setting does not seem to have any
  effect. Steps to reproduce:

  ```
  sudo apt install chaos-marmosets systemd-coredump
  sudo mkdir /etc/systemd/coredump.conf.d/
  printf "[Coredump]\nProcessSizeMax=10K\n" | sudo tee /etc/systemd/coredump.conf.d/limit.conf
  divide-by-zero
  ```

  Running `coredumpctl` shows that the dump was written in full size,
  but the ProcessSizeMax should have caused the dump to be truncated.

  ```
  TIME                           PID  UID  GID SIG    COREFILE EXE                      SIZE
  Thu 2024-01-04 14:39:44 CET 427840 1000 1000 SIGILL present  /usr/bin/divide-by-zero 17.1K
  ```

  DistroRelease: Ubuntu 23.10
  Package: systemd-coredump 253.5-1ubuntu6.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2048083/+subscriptions




More information about the foundations-bugs mailing list