Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"
Hi.
On Sat, 16 Aug 2014 02:12:48 +1200
Chris Bannister <cbannister@slingshot.co.nz> wrote:
> You mean systemd should shoulder some of the kernel's work?
A database of conflicting processes is a half-measure. Moreover, an
existing implementation of RDBMS older than systemd such as Postgres is
surely a no-go :)
You see, current Linux kernel's codebase is old, it can be traced back
to 1991. Moreover, current kernel pays little attention to Modern
FreeDesktop Standards™ (for example, kdbus). And, current kernel's
upstream cannot be considered that friendly to systemd.
To work the way it was intended - systemd upstream needs to implement
their own kernel (aka kerneld) and deprecate current one. This approach
grants virtually limitless possibilities.
For example, the problem of conflicting processes can be eliminated by
blacklisting said processes in the kerneld, whereas blacklist would be
transferred by kdbus to the current kerneld instance directly from the
https://cloud.redhat.com :)
Reco
Reply to: