Re: [systemd-devel] Where does resolved takes its data from?

FWIW the systemd 239+ version of systemd-resolve --status is resolvectl status. On Wed, Sep 5, 2018, 9:40 AM wrote: > systemd-resolved has a DBUS API, which is used by network configuration > managers such as systemd-networkd and NetworkManager to set the hostname > resolution -related configura

Re: [systemd-devel] blocking service on shutdown

Am Di., 4. Sep. 2018 um 18:53 Uhr schrieb Ralf Sieger : > > Well, it does wait when I press the power button on the case. > It does not wait if I enter as root poweroff or reboot. > I assume the first one goes through the logind while the second case does > straight to systemd... > You are correc

[systemd-devel] Potential bug where Ctrl+Alt+Del 7 times doesn't shut down the system?

I recently filed this bug with flatpak-xdg-utils: https://github.com/flatpak/flatpak-xdg-utils/issues/12 The TL;DR is that flatpak-spawn processes will cause systemd to wait for the "stop job to complete" on shutdown. Here's the systemd-relevant part: if I press Ctrl+Alt+Del 7 times, I *see* the

Re: [systemd-devel] Where does resolved takes its data from?

systemd-resolved has a DBUS API, which is used by network configuration managers such as systemd-networkd and NetworkManager to set the hostname resolution -related configuration to be used by systemd-resolved. You can see the runtime configuration of systemd-resolved by running `systemd-resol