[pve-devel] [PATCH manager] ui: node: system: avoid using 'Syslog'

Fabian Grünbichler f.gruenbichler at proxmox.com
Fri Feb 16 10:01:57 CET 2024

> Fiona Ebner <f.ebner at proxmox.com> hat am 16.02.2024 09:29 CET geschrieben:
> Am 15.02.24 um 19:20 schrieb Dietmar Maurer:
> >> The information gathered by the API call comes from the systemd
> >> journal. While 'Syslog' could be interpreted as a shorthand for
> >> "System Log", it's better to be explicit to avoid any confusion.
> > 
> >> -		title: 'Syslog',
> >> +		title: gettext('System Log'),
> > 
> > From Wikipedia: https://en.wikipedia.org/wiki/Syslog
> > 
> >> In computing, syslog /ˈsɪslɒɡ/ is a standard for message logging.
> > 
> As discussed off-list with Dietmar, the argument is that the messages
> are exactly those that are recorded via the syslog standard/mechanism.
> So "Syslog" is more precise in that sense, because "System Log" doesn't
> capture that fact and I'm retracting my patch.

while I don't mind (at all!) that that part of the UI/API is labelled syslog (I don't think it's hard to understand that it gives you the system logs of that node, and "syslog" is a bit like "Kleenex" in that regard ;)) - I do have to disagree here ;) journald does a lot more than just collecting syslog(3) messages - it also collects stdout/stderr of systemd-managed services (unless configured in a non-default fashion), messages explicitly sent to it over its own interface (like those by systemd ;)), and messages from the kernel (like dmesg), including the audit subsystem..

More information about the pve-devel mailing list