[systemd-bugs] [Bug 88986] New: standalone version of systemd to act as a process control system
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Feb 4 23:46:00 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=88986
Bug ID: 88986
Summary: standalone version of systemd to act as a process
control system
Product: systemd
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: enhancement
Priority: medium
Component: general
Assignee: systemd-bugs at lists.freedesktop.org
Reporter: sss at lambdacurry.com
QA Contact: systemd-bugs at lists.freedesktop.org
It would be great to have a feature of systemd that acts as a process control
system - similar to something like supervisord (http://supervisord.org/) or
runit (http://smarden.org/runit/)
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
(http://blog.phusion.nl/2015/01/20/baseimage-docker-fat-containers-treating-containers-vms/)
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150205/7d7c09be/attachment.html>
More information about the systemd-bugs
mailing list