> -----Original Message----- > From: development-bounces+kai.koehne=digia....@qt-project.org > [...] > Some background: on Sailfish, we launch all major system services (and > UI) through systemd services (& user session for the UI parts). Those > processes may then choose to execute processes of their own (the most > prominent example being the UI environment which will launch applications > in response to user input). With a default setup, systemd will log everything > sent to stderr of systems-launched processes, and child-launched processes > will have their stderr output attributed to the systemd service which > launched them.
Out of curiosity: Would an opt-in solution (the application explicitly has to tell Qt to log to journal, e.g. through an API, maybe even through qtlogging.ini file) work for your use case? I'm wondering whether such a setup wouldn't be a good one for desktop distributions, too. I can see that e.g. warning and errors from kwin are best kept in journald. Not sure whether that means though that you necessarily want all spurious warnings and messages from every single KDE app in there. Regards Kai _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
