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

[Benjamin Drung]

Thanks. I missed that ProcessSizeMax= only affects the generation of the
stack trace (but not the core dump file generation).

I set ProcessSizeMax=10K and the core is not stored:

```
$ journalctl -t systemd-coredump -b
Jan 04 14:11:56 systemd-coredump[426009]: The core will not be stored: size 17546 is greater than 10240 (the configured maximum)
$ coredumpctl 
TIME                           PID  UID  GID SIG    COREFILE EXE                      SIZE
Thu 2024-01-04 18:13:03 CET 452168 1000 1000 SIGILL none     /usr/bin/divide-by-zero     -
```

Shouldn't the core be truncated instead?

-- 
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