Re: Bug#876899: apt: Log to the systemd journal
- Date: Tue, 26 Sep 2017 23:51:07 +0200
- From: Julian Andres Klode <jak@xxxxxxxxxx>
- Subject: Re: Bug#876899: apt: Log to the systemd journal
On Tue, Sep 26, 2017 at 02:46:55PM -0400, Jeremy Bicha wrote:
> Source: apt
> Version: 1.5
> Severity: wishlist
> Ubuntu 17.10 has switched from the unmaintained gnome-system-log app
> to gnome-logs by default. While gnome-system-log is a traditional log
> viewer, gnome-logs only displays logs from systemd. apt was identified
> as a particular part of the system that doesn't use systemd logging
> and so this is a regression compared to previous Ubuntu releases.
> I expect Debian will need to maintain the ability to emit traditional
> logs without using systemd's journal. It makes sense to me for apt on
> Ubuntu to use systemd logging by default, but I think it makes sense
> on Debian too. At least on Ubuntu, it would make sense to *only* log
> to the systemd journal (systemd can be configured to create
> traditional logs for users that want that).
So, not discussing about usefulness or not but practical aspects:
- chroots would also log in the machine journal, which is wrong
- same for some other weird temporary chroot thingies
- term.log might contain sensitive data that should not be
easily available (I think)
- dpkg.log and update-alternatives.log are more detailed step-by-step
Maybe someone on debian-devel has some more opinion, but I'm not sure
if it is worthwhile pursuing this.
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.