Re: [systemd-devel] PAMName=login, systemctl stop

On Mo, 03.07.23 15:21, Andrei Borzenkov (arvidj...@gmail.com) wrote: > On 03.07.2023 14:17, Lennart Poettering wrote: > > On Mo, 03.07.23 10:58, Valentijn Sessink (valent...@sessink.nl) wrote: > > > > > Now my remaining question is probably so very basic, that you sort of > > > missed > > > it:

Re: [systemd-devel] bind-mount of /run/systemd for chrooted bind9/named

On Mon, Jul 03, 2023 at 11:21:22PM +0200, Silvio Knizek wrote: > why is it suggested to run `named` within its own chroot? For security > reasons? This can be achieved much easier with systemd native options. That feature is two decades older than systemd, and name server operators are darn

Re: [systemd-devel] bind-mount of /run/systemd for chrooted bind9/named

On Mo, 03.07.23 20:52, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > (1) go fully systemd > That would mean to get rid of bind's -t option completely but use > systemd's RootDirectory directive instead. I have not tried this but I > think that the bind community might be reluctant to

[systemd-devel] Why is my reboot.target disabled?

Hi, Please help me understand this phenomenon (systemd 252): $ systemctl status ctrl-alt-del.target ○ reboot.target - System Reboot Loaded: loaded (/lib/systemd/system/reboot.target; disabled; preset: enabled) Active: inactive (dead) Docs: man:systemd.special(7) $ ls -l

Re: [systemd-devel] Why is my reboot.target disabled?

On 04.07.2023 14:58, Ferenc Wágner wrote: Hi, Please help me understand this phenomenon (systemd 252): $ systemctl status ctrl-alt-del.target ○ reboot.target - System Reboot Loaded: loaded (/lib/systemd/system/reboot.target; disabled; preset: enabled) Active: inactive (dead)