> On Tue, Sep 27, 2022, at 10:59 AM, Chris Murphy wrote: > > I hadn't considered the container case at all, that containers running > systemd-journald would have their own journals and retention policy. I wonder if the > container default should have volatile journals? Or forward the journals to the host by > default? But yes I can see how many containers each thinking they have a 4G cap could > quickly become a problem. To be fair, my situation might be a bit unorthodox. These systemd-nspawn containers were created using `dnf --installroot ...` (the sort of method documented here: http://0pointer.net/blog/systemd-for-administrators-part-xxi.html). And some of them were created by copying the root filesystems of what were formerly qemu virtual machines. I'm not sure how common that sort of thing is for people to do. As long as it is easy for admins to tweak things for their use case, it might not be something that really needs a special default. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
