systemd journald instead of own log?

[technobirb]

Is it possible for qBittorrent to use systemd journald instead of managing its own log?
From my experience with other apps, I think it might be as simple as writing messages to stdout when it's run as a service.

[CedricConday]

No. The only sink for the message log is the file logger: src/app/filelogger.cpp opens <FileLogger\Path>/qbittorrent.log with QFile in append mode, and nothing in src/app/ or src/base/logger.cpp writes log messages to stdout, syslog or the journal. Under the shipped dist/unix/systemd/qbittorrent-nox@.service.in the journal therefore only gets the startup and WebUI errors that main.cpp prints to stderr. A stdout or console logger is feature request #10077, open since 2018.

Two workarounds, depending on where it runs:

• In a container, where stdout is a pipe, the symlink from Redirect qBittorrent log messages to stdout #10077 works: ln -sf /proc/self/fd/1 <profile>/qBittorrent/data/logs/qbittorrent.log.
• Under systemd it does not: with StandardOutput=journal fd 1 is a unix socket, and open() on /proc/self/fd/1 fails with ENXIO (tested), so QFile::open fails and you get a critical "could not be opened" log entry instead. Feed the file to the journal from outside, e.g. a small companion unit running tail -F <profile>/qBittorrent/data/logs/qbittorrent.log | systemd-cat -t qbittorrent-nox.

The directory is FileLogger\Path under [Application] in qBittorrent.conf; FileLogger\Enabled=false only turns file logging off, it redirects nothing.