Clarifications and overview of functionality

[matu3ba]

"If anyone can shed light on what some of the more mysterious parameters do please let me know!"
You can steal copy examples from here

Overview of functionality

"Keeping track of users and sessions, their processes and their idle state" and "shutdown/sleep inhibition logic for applications" is missing from the big pictures, which could link as table of contents.

It would be probably easier to just copy-paste these images and remove/add an appendix section for libinput and udev, since logind does only do the file-descriptor handling.

"This could probably be done by using the posix sessionids in most cases. But those are not reliable since processes can leave their session and make a new one. Now we don't know anymore what is going on!"
Examples for cases would help here

Writing udev functionality as a list ( defining set of hardware as Seat, ... ) would certainly help readability.

[KillingSpark]

Thanks, I'll keep this in mind when I edit the document to clarify some of the open questions from #3

[KillingSpark]

You can steal copy examples from here

I might just be too blind to find the examples, but I dont see them. Could you give me a pointer? I only see API definitions and more or less detailed descriptions of the functions.

[matu3ba]

@KillingSpark Sorry, I was wrong on that.

From some conversations on reddit, the main source of complexity is due to possibly malfunctioning programs and tracking of double-forks and alike. This should be the only purpose of systemd as a library, but there is no specification so it is not enforced.

All the other stuff appears to me be bloated due to missing specification.