Please let me add something. Am 19.07.2023 09:12 schrieb c.buhtz@posteo.jp:
"_SYSTEMD_UNIT" : "session-4.scope", "_PID" : "2796", "_COMM" : "python3", "MESSAGE" : "backintime (user/1): INFO: Unlock",
BIT itself do set the syslog identifier to "backintime (user/1)". But somehow this is ignored or overwritten and inserted to the message itself. And the journalctl entry then even do not have a SYSLOG_IDENTIFIER field. I'm not an admin in the unix world. Maybe they find journalctl/syslog helpfull but I don't. We have one "simple" userspace application using syslog and it is not possible to reliable find all its entries in the logs. Using "grep" is not reliable but just a workaround. Maybe some BIT users do use that logs. So I won't remove that behavior. But I really think about if it would help BIT to have an application specific log-file. For thous who are not able to use journalctl or don't trust it such a plain log file would help doing diagnosis especially for us as developers. Implementing this is not a big deal. Python offer nice features about it. Even having multiple BIT instances (e.g. backintime-qt and backintime) logging the same time is no problem. I do have a solution in my mind. ;) Am I the only one having problems with journalctl/syslog?