--- 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: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" 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..
>
> IMHO, those are just Implementation details of systemd init..
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
--- End Message ---
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
