Re: dpkg-conffile handling in einer systemd-Welt
Michael Biebl <biebl@debian.org> wrote:
> Um schnell einen Überblick zu bekommen, was man lokal abgeändert hat,
> kann man systemd-delta verwenden. Das könnte man evtl. sogar mit einem
> apt-hook in den upgrade Prozess einbinden.
Irgendwie kommt systemd-delta (215-18) aber nicht mit generierten Units
klar.
Ich habe, wie in einer andere Mail beschrieben, ein Drop-In für
getty@tty1, aber systemd-delta zeigt dies nicht an:
,----
| ~# systemd-delta
| [EXTENDED] /run/systemd/system/session-62057.scope → /run/systemd/system/session-62057.scope.d/50-SendSIGHUP.conf
| [EXTENDED] /run/systemd/system/session-62057.scope → /run/systemd/system/session-62057.scope.d/50-After-systemd-user-sessions\x2eservice.conf
| [EXTENDED] /run/systemd/system/session-62057.scope → /run/systemd/system/session-62057.scope.d/50-After-systemd-logind\x2eservice.conf
| [EXTENDED] /run/systemd/system/session-62057.scope → /run/systemd/system/session-62057.scope.d/50-Description.conf
| [EXTENDED] /run/systemd/system/session-62057.scope → /run/systemd/system/session-62057.scope.d/50-Slice.conf
| [EXTENDED] /run/systemd/system/session-62047.scope → /run/systemd/system/session-62047.scope.d/50-SendSIGHUP.conf
| [EXTENDED] /run/systemd/system/session-62047.scope → /run/systemd/system/session-62047.scope.d/50-After-systemd-user-sessions\x2eservice.conf
| [EXTENDED] /run/systemd/system/session-62047.scope → /run/systemd/system/session-62047.scope.d/50-After-systemd-logind\x2eservice.conf
| [EXTENDED] /run/systemd/system/session-62047.scope → /run/systemd/system/session-62047.scope.d/50-Description.conf
| [EXTENDED] /run/systemd/system/session-62047.scope → /run/systemd/system/session-62047.scope.d/50-Slice.conf
| [EXTENDED] /run/systemd/system/session-52074.scope → /run/systemd/system/session-52074.scope.d/50-SendSIGHUP.conf
| [EXTENDED] /run/systemd/system/session-52074.scope → /run/systemd/system/session-52074.scope.d/50-After-systemd-user-sessions\x2eservice.conf
| [EXTENDED] /run/systemd/system/session-52074.scope → /run/systemd/system/session-52074.scope.d/50-After-systemd-logind\x2eservice.conf
| [EXTENDED] /run/systemd/system/session-52074.scope → /run/systemd/system/session-52074.scope.d/50-Description.conf
| [EXTENDED] /run/systemd/system/session-52074.scope → /run/systemd/system/session-52074.scope.d/50-Slice.conf
| [EXTENDED] /run/systemd/system/session-7.scope → /run/systemd/system/session-7.scope.d/50-SendSIGHUP.conf
| [EXTENDED] /run/systemd/system/session-7.scope → /run/systemd/system/session-7.scope.d/50-After-systemd-user-sessions\x2eservice.conf
| [EXTENDED] /run/systemd/system/session-7.scope → /run/systemd/system/session-7.scope.d/50-After-systemd-logind\x2eservice.conf
| [EXTENDED] /run/systemd/system/session-7.scope → /run/systemd/system/session-7.scope.d/50-Description.conf
| [EXTENDED] /run/systemd/system/session-7.scope → /run/systemd/system/session-7.scope.d/50-Slice.conf
| [EXTENDED] /lib/systemd/system/fail2ban.service → /etc/systemd/system/fail2ban.service.d/after-ferm.conf
`----
Es stellt nur das Drop-In für fail2ban dar.
S°
--
Sigmentation fault. Core dumped.
Reply to: