News for hackers. Stuff that matters.
Re:Debian reconsiders init-system diversity by ibotty on Tuesday November 12, 2019 @04:21AM (#21512753)
It also gets back logs from journald! How do you envision `systemctl status $unit` to show the last logs if they are in some random log file?
Re:Debian reconsiders init-system diversity by newnewpdro on Tuesday November 12, 2019 @04:38AM (#21512808)
First of all, no, systemd as in PID1 does not get logs back from journald. The systemctl command is using the sd-journal API to do that directly from the journal files.

Secondly, I don't, I expect the recent logs portion of `systemctl status $unit` to be suppressed when journald isn't present.

Note that journal-caused slowness of that very command is a common complaint aimed at journald contributing to people wanting to remove it!

Re:Debian reconsiders init-system diversity by kungtotte on Tuesday November 12, 2019 @12:15PM (#21515823)
With runit, for example, logs are put in a canonical per-service directory.

E.g. `service_directory/service/logs`

Seems like a trivial way to solve it...

Re:Debian reconsiders init-system diversity by ibotty on Wednesday November 13, 2019 @02:46AM (#21521875)
Yes, of course that's possible. But that's no generic syslog daemon either.