Friedrich Weber <f.we...@proxmox.com> writes:
> If I read the journald.conf docs [1] right, the default interval is 30s > and the burst value is 10000 multiplied by a factor depending on the > free disk space, I guess 4-6 on reasonable setups -- this is a lot of > messages, but as you mention probably fine for limiting really noisy > services. I was more thinking about this from a technical support > point-of-view, where I'd fear that having extreme corosync logspam over > days or weeks would cause the actually interesting stuff to be rotated > away more quickly than I'd like. :) > > But as we have no idea how many broken setups are out there, this is all > somewhat hypothetical, so I'm also fine with not applying this -- if we > get many user reports seeing logspam I guess we can still do this. > > [1] > https://www.freedesktop.org/software/systemd/man/latest/journald.conf.html#RateLimitIntervalSec= I am starting to lean towards not limiting this here. However, I have seen multiple instances at our support portal where logs are rotated rather quickly and useful messages are lost. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
