> Maybe a simple replacement for logind in this scenario is possible
> You could resurrect ConsoleKit and port the patches going into systemd-logind to it.
Also, running logind does not require running, or even installing, systemd (though you can't build one without building the other). An upstart/logind or sysvinit/logind setup would require slightly more configuration than a systemd/logind setup, but really no more (but of course different) configuration compared to an upstart/ConsoleKit or sysvinit/ConsoleKit setup, so not out of reach of the distro packagers.
Posted Sep 19, 2013 13:23 UTC (Thu) by ABCD (subscriber, #53650)
[Link]
As of systemd-205, this is no longer true. In that version, systemd-logind lost support for creating its own cgroups (which it requires to operate), instead delegating that responsibility to systemd, which already has to be able to create them for its own purposes.
The end of the 3.12 merge window
Posted Sep 23, 2013 7:08 UTC (Mon) by kugel (subscriber, #70540)
[Link]
So there goes the promised modularity of the systemd codebase. It seems the project's statements are not dependable after all.
The end of the 3.12 merge window
Posted Sep 23, 2013 16:12 UTC (Mon) by mathstuf (subscriber, #69389)
[Link]
This actually makes sense since systemd is on its way to being /the/ cgroup manager. Taking logind and patching it to call your own cgroup manager (or patching the functionality back in) is probably easier than resurrecting ConsoleKit.
