https://bugs.kde.org/show_bug.cgi?id=368114
Edward Donovan <kde-b...@numble.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kde-b...@numble.net
--- Comment #1 from Edward Donovan <kde-b...@numble.net> ---
Yes, this is happening here, too, with KTorrent 5. A flood of messages is
printed to stdout, and I have to work around it for now by setting up a custom
desktop file to run ktorrent with stdout redirected to /dev/null.
After a bunch of digging, it looks like this is set in the libktorrent code, in
util/log.h at line 97:
void setOutputToConsole(bool on);
The comments say:
* By default all messages will also be printed on the standard output. This
* can be turned down using the @a setOutputToConsole function.
I don't know all the reasons that default may have been chosen... From my
experience, I'd be delighted if the default for general distribution was
changed to 'off'. :)
If not, is it a matter of where the log level is chosen, somewhere else, and
the problem is that we're getting all these LOG_NOTICE and some LOG_DEBUG
messages?
This is echoing what Knut said, but here's the impact this is having: Over
several days of running ktorrent off and on, my .xsession-errors file has grown
to over a gigabyte. The vast majority of that file is ktorrent's messages. I
first noticed this problem when trying to find another program's diagnostics in
.xsession-errors; it becomes a bit of a DOS attack against trying to find
anything in that file. :) I haven't done a performance analysis, but from past
experiences, I would think the heavy logging would have at least some
performance impact?
Thank you, if you'll consider this. And thank you for KTorrent!
(I'm running the Fedora rawhide package of ktorrent 5.0.1, under fedora 25. I
got the package from
https://rpmfind.net/linux/RPM/fedora/devel/rawhide/x86_64/k/ktorrent-5.0.1-3.fc26.x86_64.html
)
--
You are receiving this mail because:
You are watching all bug changes.
