Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is there a good way for non-root users to start "managed" processes? In this case, I am using managed" to describe a process that starts up when the user logs in, is monitored by some sort of process supervisor (like init), restarted if it fails, and has its stdout/stderr logged somewhere automatically.

I have over time hacked together a few solutions on my own running something like runit or supervisor, but neither has been particularly well integrated into my desktop environment or the system in general. Is there a standard solution for this sort of thing?

share|improve this question
The closest I've seen is runit's user-controlled services, which is a pity that it's not used more often, if only because there isn't a huge API layer or CPU-gobbling overhead involved in the setup. The systemd folks are pushing hard right now, and I suspect it will be a matter of time before someone has the same idea with it. – Avery Payne Sep 3 '14 at 1:10
Wow, this is an old question :). systemd now has support for user-controlled services, e.g. as documented here. – larsks Sep 3 '14 at 1:48
Indeed. I only recently started with runit for personal use because I wasn't a fan of systemd's "all in one" approach. As far as machines at work go, I don't care if they run systemd or not, I only care that they stay up and running. :) – Avery Payne Sep 4 '14 at 18:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.