<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - standalone version of systemd to act as a process control system"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88986">88986</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>standalone version of systemd to act as a process control system
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>sss@lambdacurry.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>It would be great to have a feature of systemd that acts as a process control
system - similar to something like supervisord (<a href="http://supervisord.org/">http://supervisord.org/</a>) or
runit (<a href="http://smarden.org/runit/">http://smarden.org/runit/</a>)
The problem is that the number of process supervisors to be used has increased:
1. upstart for older deb systems
2. supervisord/runit for running applications (Ruby on Rails, Python, Go, etc.)
3. supervisord/runit to run Docker containers
(<a href="http://blog.phusion.nl/2015/01/20/baseimage-docker-fat-containers-treating-containers-vms/">http://blog.phusion.nl/2015/01/20/baseimage-docker-fat-containers-treating-containers-vms/</a>)
4. systemd in newer linux versions.
I do not believe we will upgrade older computers to newer OS running systemd
anytime soon, but it would be great if there was a way we could use
systemd+journald in older OS to run applications. This would atleast eliminate
the need to use supervisord/runit and give us a path to migrate to systemd.
Otherwise, I suspect that people will use supervisord/runit far more in
production (+docker) than systemd ..... and will continue to use it even on
newer systems, simply because of inertia.
I do understand that systemd needs to be pid 1, but I wonder if a subset of
functionality can still be exposed when it is not running as pid 1.... atleast
as good as supervisord.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>