Boucman

hmm, when swayidle tells logind that the system is idle, IIUC logind will lock all the sessions (for the lock action) of all users. it's a bit more complicated than...

if the point of daemonization is systemd, maybe it would be better to adapt swayidle for Type=notiy instead ? forking is very hard to do correctly, and is not very...

why not ?

let me reiterate... from systemd's point of view, Type=notify is strictly better than Type=forking. It's easier to code (no need to fork or sychronize the child with the parent) and...

please have a read of https://man7.org/linux/man-pages/man7/daemon.7.html https://man7.org/linux/man-pages/man3/daemon.3.html making a daemon is "a bit" more involved than just forking...

well, you should at least make sure stdin/stdout are properly handled, wihich implies you have to do the double-fork dance...

Type= is about readiness. It tells systems at what point swayidle is ready to do its job. Once swayidle is ready, systemd is allowed to start any other service that...

I don't know user-session integration very well, so I might not have the knowledge to do a proper review... related documentation is here : https://systemd.io/DESKTOP_ENVIRONMENTS/ but I never had to...

you have Requires=graphical-session.target so if swayidle.service is enabled, then graphical-session will be activated (by swayidle) what you describe is the WantedBy part (which is correct) I have doubts about the...

That's look good. the Restart=always means that swayidle will always be restarted, except when explicitely stopped by systemd itself. in particular, it will be restarted if it stops "cleanly" I...