On Sat, Jun 29, 2024 at 4:22 PM Luca Boccassi wrote:
>
> On Sat, 29 Jun 2024 at 21:16, Mike Gilbert wrote:
> >
> > I recently added systemd v256 to Gentoo's ebuild repo. While testing
> > the upgrade process from v255, I have run into an issue.
> >
> > After the upgrade, my KDE Plasma session sto
On Sat, 29 Jun 2024 at 21:16, Mike Gilbert wrote:
>
> I recently added systemd v256 to Gentoo's ebuild repo. While testing
> the upgrade process from v255, I have run into an issue.
>
> After the upgrade, my KDE Plasma session stopped working, and I was
> unable to execute a reboot from the GUI.
>
v255 added a new systemd-executor binary – instead of direct
fork/setup/exec, now it's fork/exec(executor)/setup/exec(service), to avoid
doing too much stuff after fork. But the binary is executed off an open fd,
so even though you've upgraded it on disk, the manager is still holding
onto its old c
I recently added systemd v256 to Gentoo's ebuild repo. While testing
the upgrade process from v255, I have run into an issue.
After the upgrade, my KDE Plasma session stopped working, and I was
unable to execute a reboot from the GUI.
Looking at the journal, I see several messages like this one:
Hey guys, I have question regarding a certain behaviour of the systemd
mount generator.
Mounts do not have `Before=*-fs.target` if the `nofail` mount option is
added to their `/etc/fstab` entry.
From the man page I see that this is intended behaviour:
-
https://www.freedesktop.org/software/s
