On Apr 4, 2015, at 4:08 PM, J Martin Rushton <martinrushton56 at btinternet.com> wrote: >> This is a quite messy though as you're running a 'system service' >> in the context of a regular user.... you were better off doing >> this within the user space as you started with. > > It's getting rather windozy though if proper background system stuff > is moved into user space. Multiple definitions of the D: drive > anyone? :-( And of course, that's not at all what running systemd user services is about. Its possible to have systemd start up a separate systemd process for each user, to manage user-based services (such as your example), but run outside of your login session, with all the resource management/cgroups and logging features you get with systemd. I'm not really thrilled with the service, though. Since it operates outside of user login sessions, anyone who uses homedirs that require network authentication (such as NFS w/ sec=krb5 or OpenAFS) can't use it at all, since it looks in ~user/.config/systemd/ for services. -- Jonathan Billings <billings at negate.org>