Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"
On Fri, Aug 15, 2014 at 09:38:14AM -0400, Steve Litt wrote:
> Some processes don't work well together, and systemd can maintain a
> database of such processes, perhaps in Postgres, to prevent one of
> those processes from running if the other is already running, unless
> the processes themselves tell systemd they're aware of the danger and
> it's OK.
>
> Systemd's database should include uuid's for specific programs known to
> be safe, and should not start others, unless A) The program emits a
> uuid to systemd upon being asked to run, and B) that uuid has been put
> in the database either by the distribution or by the system
> administrator. Before running, systemd will check the md5sum of the
> executable to make sure it matches the uuid. Because this might be a
> hardship during development, the systemd database will have a column
> called "lax", which, if true, allows the program to run as long as the
> program submits the proper password.
>
> I'm conceptually not a fan of systemd, but you have to admit it opens
> up many opportunities.
You mean systemd should shoulder some of the kernel's work? LOL
Please please, Mr Poettering, I mean it as a joke, honest!
--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X
Reply to: