Is this with cgroups v1 or v2? If cgroups v1 is involved (thanks Docker), I
recall it was a bit complex for systemd to get notified when the cgroup
actually empties – via /sys/fs/cgroup/systemd/release_agent that specifies
a helper executable that the kernel runs... I wonder if that mechanism is
br
I'm seeing "systemctl stop " for several services taking a
long time because it goes through the timeout process, even though all
relevant processes have exited.
I'll give 2 examples. Both examples are running inside a privileged
Rocky Linux 8.8 Docker container on a Rocky Linux 8.8 host. The
sy
I figured out how to do this, sorta. I ended up bypassing the
systemd-cryptsetup mechanism entirely and instead wrote my own shell
script and systemd unit that did things exactly the way I wanted. Now if
the user provides the right password, their home dir is mounted, if they
type a wrong one t
On Mo, 09.10.23 12:07, Tony Rodriguez (unixpro1...@gmail.com) wrote:
> Created a service that invokes a "systemctl daemon-reload". Goal is for a
> reload to occur early in the boot process, before other user made services
> are invoked. During additional testing, sometimes it is correct and other
