https://bugs.kde.org/show_bug.cgi?id=494632
pallaswept <pallasw...@proton.me> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pallasw...@proton.me
--- Comment #2 from pallaswept <pallasw...@proton.me> ---
(In reply to Peter Eszlari from comment #1)
> 10000+ messages in 30s seems quite high to me, but I guess this isn't
> strictly a bug then.
Hi Peter!
I've been bitten by this issue quite a few times. A single errant app can
render my entire journal un-usable, but of course, I won't know of it until
much later when I actually need to read the journal, and effectively can't,
because it's so big that it can take hours to open it. I hadn't had the time to
chase that bug yet, so I'm glad you did, and I just stumbled across it. Until
now, I've been deleting my logs and wondering what was in them.
Knowing that there is actually a rate limiter, I'm of the very strong opinion
that it's set far, far too loosely by default, and I doubt very much that this
is intentional behaviour, that normal usage can effectively break the journal
entirely... so maybe it really is a bug.
I think this should be reported upstream, so they can decide if that's how they
wanted it to act. I don't want to hijack your issue, so let me know if you'd
rather do it, or if you'd rather not, and I'll do it :)
In the meantime, I'll modify the config and give you my thanks for looking into
this!
--
You are receiving this mail because:
You are watching all bug changes.
