Am 03.04.2014 16:19, schrieb Michael Biebl: > Am 03.04.2014 16:03, schrieb Michael Biebl: >> I think the way to address is, is to make systemd-logind not send out >> the "Suspending" D-Bus signal when there is no way the suspend request >> will be processed. >> >> My immediate idea was to stick a sd_booted() check into logind, but >> unfortunately it's not quite as simple. With systemd-shim around, such a >> suspend request can actually work for PID 1 != systemd as it would be >> handled by the systemd-shim process (which is D-Bus activated on-demand). >> >> So we probably need a different approach, like logind doing a D-Bus Ping >> to the org.freedesktop.systemd1 interface to see if there would be >> process handling the suspend/hibernate request.
One more thought: It's not yet clear what the future of systemd-shim will be post systemd-204 and if we can continue to make systemd-logind as provided by the systemd package work standalone. If we remove the patches to make systemd-logind activatable under PID 1 != systemd those issues would simply go away. Of course this would cause other issues, like making package as network-manager depend on PID 1 = systemd to be usable. Should we postpone a fix until we have a clearer picture how things will evolve regarding logind in the future? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
