Running akonadictl in a Konsole to do anything (like restart akonadi, which can be a per-hour thing that needs doing) makes that Konsole receive every subsequent warning or error message that akonadi emits, until that Konsole is closed. Reproducible: Always Steps to Reproduce: 1. Open a Konsole, run akonadictl restart (for example) 2. See how much akonadi writes to stdout (I presume) 3. leave that Konsole open for a while 4. See all that akonadi emits into that Konsole, rather than to some log file Actual Results: For anything but a situation in which akonadi is working properly (are there any?), the Konsole will be full of messages. Expected Results: Like systemctl, there should be nothing written to stdout after the command has been run.
Invalid. You restart it so you will show warning in console.
On Thursday, July 04, 2013 09:52:25 AM Laurent Montel wrote: > https://bugs.kde.org/show_bug.cgi?id=321943 > > Laurent Montel <montel@kde.org> changed: > > What |Removed |Added > ------------------------------------------------------------------------- > --- Status|UNCONFIRMED |RESOLVED > CC| |montel@kde.org > Resolution|--- |INVALID > > --- Comment #1 from Laurent Montel <montel@kde.org> --- > Invalid. > You restart it so you will show warning in console. Why does it show me warnings forever? Systemctl (and service before it) doesn't. With the number of messages akonadi can put out, endlessly, this makes it necessary to open a Konsole just to run akonadictl and then close it.
if you don't want some debug output in a console, restart it using krunner. alt-f2 + akonadictl restart