Re: MS is trapped
This is how systemd is destroying Linux:
- I wonder what the status of my cluster is...
systemctl status pcsd.service
pcsd.service - PCS GUI and remote configuration interface
Loaded: loaded (/usr/lib/systemd/system/pcsd.service; enabled)
Active: active (running) since Tue 2015-03-31 18:20:38 BST; 18h ago
Main PID: 577 (pcsd)
CGroup: /system.slice/pcsd.service
├─577 /bin/sh /usr/lib/pcsd/pcsd start
├─593 /bin/bash -c ulimit -S -c 0 >/dev/null 2>&1 ; /usr/bin/ruby -I/usr/lib/pcsd /usr/lib/pcsd/ssl.rb
└─594 /usr/bin/ruby -I/usr/lib/pcsd /usr/lib/pcsd/ssl.rb
systemctl status corosync.service
corosync.service - Corosync Cluster Engine
Loaded: loaded (/usr/lib/systemd/system/corosync.service; enabled)
Active: active (running) since Tue 2015-03-31 18:20:47 BST; 18h ago
Process: 1558 ExecStart=/usr/share/corosync/corosync start (code=exited, status=0/SUCCESS)
Main PID: 1652 (corosync)
CGroup: /system.slice/corosync.service
+-1652 corosync
Mar 31 18:20:46 nsa00.systemd.willeat.your.babies.com corosync[1652]: [VOTEQ ] Waiting for all cluster members. Current votes: 1 expected_votes: 2
Mar 31 18:20:46 nsa00.systemd.willeat.your.babies.com corosync[1652]: [QUORUM] Members[1]: 1
Mar 31 18:20:46 nsa00.systemd.willeat.your.babies.com corosync[1652]: [MAIN ] Completed service synchronization, ready to provide service.
Mar 31 18:20:46 nsa00.systemd.willeat.your.babies.com corosync[1652]: [TOTEM ] A new membership (192.168.56.31:68) was formed. Members joined: 2
Mar 31 18:20:46 nsa00.systemd.willeat.your.babies.com corosync[1652]: [VOTEQ ] Waiting for all cluster members. Current votes: 1 expected_votes: 2
Mar 31 18:20:46 nsa00.systemd.willeat.your.babies.com corosync[1652]: [QUORUM] This node is within the primary component and will provide service.
Mar 31 18:20:46 nsa00.systemd.willeat.your.babies.com corosync[1652]: [QUORUM] Members[2]: 1 2
Mar 31 18:20:46 nsa00.systemd.willeat.your.babies.com corosync[1652]: [MAIN ] Completed service synchronization, ready to provide service.
Mar 31 18:20:47 nsa00.systemd.willeat.your.babies.com corosync[1558]: Starting Corosync Cluster Engine (corosync): [ OK ]
Mar 31 18:20:47 nsa00.systemd.willeat.your.babies.com systemd[1]: Started Corosync Cluster Engine.
Great, systemd is giving me way more information and control than ever before, and it is modernizing the painful daemon/service management in Linux I must oppose it vehemently!