SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
SoylentNews
elias writes:
"A very public and sometimes acrimonious dispute in the Debian ecosystem about upstart versus systemd has been settled in favour of systemd. Some go as far as to brand it a new era after the Linux civil war [Beware popups].
We also had an asksoylentnews question on what the fuzz was all about. But what can upstart contribute to systemd now the war is over, or will it simply be a technology that we remember fondly, but do not see any more in a few years time?"
This discussion has been archived.
No new comments can be posted.
Ubuntu Concedes Defeat in Upstart vs Systemd
|
Log In/Create an Account
| Top
| 41 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Your lucky number is 3552664958674928. Watch for it everywhere.
(Score: 2) by tibman on Wednesday March 19 2014, @07:12PM
It has to do with a service manager that actually knows the state of various services and continuously monitors them. sysvinit doesn't really do this;
You're looking for rc-status. It shows you each service and its current state. Similar to if you run the service script with status at the end. Like "/etc/init.d/apache2 status".
Though a bit of a text blob, here is actual output (butchered to fit) from rc-status where i've manually killed mysql. Mysql is reported as "crashed". This is a good cli representation of my current running services and their state.
Runlevel: default
sshd [ started ]
dhcpcd [ started ]
net.eth0 [ started ]
netmount [ started ]
ntpd [ started ]
vixie-cron [ started ]
local [ started ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed
Dynamic Runlevel: manual
mysql [ crashed ]
apache2 [ started ]
SN won't survive on lurkers alone. Write comments.