journalctl --vacuum-size=0 does nothing

[abitrolly]

systemd version the issue has been seen with

251

Used distribution

Fedora 37

Linux kernel version used

kernel-6.2.10-200.fc37.x86_64

CPU architectures issue was seen on

x86_64

Component

journalctl

Expected behaviour you didn't see

$ sudo journalctl --vacuum-size=0
Vacuuming done, freed 0B of archived journals from /var/log/journal.
Vacuuming done, freed 0B of archived journals from /run/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal/c3b1f5b205ed4158bd61c304044f4bb7.
$

Unexpected behaviour you saw

$ sudo journalctl --vacuum-size=0
$

Steps to reproduce the problem

sudo journalctl --vacuum-size=0

Additional program output to the terminal or log subsystem illustrating the issue

No response

[abitrolly]

The same problem with --vacuum-files=0 and --vacuum-time=0.

[mrc0mmand]

This is expected and documented.

From journalctl(1) man page:

--vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a single invocation to enforce any combination of a size, a time and a number of files limit on the archived journal files. Specifying any of these three parameters as zero is equivalent to not enforcing the specific limit, and is thus redundant.

[abitrolly]

This is expected and documented.

Are you sure it is expected? Normally I would rely on UX research or at least a poll to gather the proof.