--- Begin Message ---
Another random find today in man 8 rasdaemon [1], a post Syslogd-only era tool:
> These trace events are logged in /sys/kernel/debug/tracing, reporting them
> via syslog/journald.
[1] https://manpages.debian.org/testing/rasdaemon/rasdaemon.8
On Fri, Feb 16, 2024 at 10:25:2
--- Begin Message ---
Just a small random addition to the rabbithole of the term syslog and that it
has been source of confusion since long.
There's yet another syslog, completely unrelated:
# man 2 syslog:
DESCRIPTION
Note: Probably, you are looking for the C library function
sy
--- Begin Message ---
On Thu, Feb 15, 2024 at 07:20:51PM +0100, Dietmar Maurer wrote:
> > 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.
>
> > -
--- Begin Message ---
On Fri, Feb 16, 2024 at 10:25:22AM +0100, Dietmar Maurer wrote:
> > 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
> 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 c
Am 16.02.24 um 10:01 schrieb Fabian Grünbichler:
>
>> Fiona Ebner 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
>>
> Fiona Ebner 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 an
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',
>> +
Am 15.02.24 um 19:25 schrieb Dietmar Maurer:
> I can also imaging using "Events" instead of "Syslog".
>
> - title: 'Syslog',
> + title: gettext('Events'),
>
> IMHO this is easier to translate.
>
Then at least "System Events". Otherwise it leaves the question "what
kind o
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',
>> +
I can also imaging using "Events" instead of "Syslog".
- title: 'Syslog',
+ title: gettext('Events'),
IMHO this is easier to translate.
> With your change:
>
> - title: 'Syslog',
> + title: gettext('System Log'),
>
> we now need to translate
> 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: htt
Reported in the community forum [0]. Since Proxmox VE 8/Debian 12,
rsyslog is not installed by default for new installations anymore [1].
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 e
13 matches
Mail list logo
