systemd user session integration (Auke Kok)
raphgro at web.de
Sat Jun 30 14:20:30 CEST 2012
FYI, there's already an open RFE bug for systemd.
Please consider to do the discussion there to lower traffic on the ml.
Thanks for your motivation to work on systemd.
> Date: Fri, 29 Jun 2012 22:39:32 -0700
> From: Auke Kok <auke at foo-projects.org>
> To: XFCE4 development list <xfce4-dev at xfce.org>
> Subject: systemd user session integration
> Message-ID: <4FEE9114.2080201 at foo-projects.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> I'd like to start a quick project to properly integrate Xfce4 with
> systemd. There are several parts needed here, but it's not too hard
> to do so.
> Some concepts, before we start:
>  systemd starts everything. No cheating and forking off helper
> processes  socket activation is better than dbus activation is
> better than launching
>  processes involved should signal when they are "complete" or
> What I've done so far with systemd --user:
> - start xfce4-session through a service file
> - pray it all works
> What I'd like to see/create:
> - a comprehensive non-xfce4 session based way of starting most xfce4
> components through separate systemd unit files without xfce4-session
> starting them for us.
> - socket activation for services that are socket-based (?)
> - dbus activation for services that are dbus based (xfconfd)
> - sd-notify() usage for each of the daemons to signal when they are
> - xfce4-session can stay but should not start things like Thunar
> --daemon, xfdesktop etc. under a systemd --user session
> - logind integration in systemd.
> The end result should use pkg-config "systemd" and be conditional on
> the return value - rather trivial of course (man 7 daemon).
> Anyone interested in working with me in figuring out the bits needed
> to improve this part?
> Xfce4-dev mailing list
> Xfce4-dev at xfce.org
> End of Xfce4-dev Digest, Vol 103, Issue 18
More information about the Xfce4-dev