The Grumpy Editor's guide to surviving the systemd debate
The Grumpy Editor's guide to surviving the systemd debate
Posted Nov 13, 2014 18:06 UTC (Thu) by bronson (subscriber, #4806)In reply to: The Grumpy Editor's guide to surviving the systemd debate by rvfh
Parent article: The Grumpy Editor's guide to surviving the systemd debate
Posted Nov 16, 2014 11:22 UTC (Sun)
by jonnor (guest, #76768)
[Link] (2 responses)
Posted Nov 17, 2014 12:37 UTC (Mon)
by peter-b (subscriber, #66996)
[Link]
Posted Nov 17, 2014 13:41 UTC (Mon)
by rvfh (guest, #31018)
[Link]
I also run the upgrades on that one to make sure things don't break before upgrading the rest :-)
Posted Nov 17, 2014 13:46 UTC (Mon)
by rvfh (guest, #31018)
[Link]
Seems I did not commit the upstart one but I can do if that's of interest to somebody (I'll have to test it first though...)
Also, I am not sure the sysvinit one is on par with the systemd one, as systemd restarts my daemon if it disappears for any reason...
The Grumpy Editor's guide to surviving the systemd debate
In general I'd recommend not installing the package which replaces /sbin/init until working with init=/bin/systemd has been confirmed. Its just good practice.
The Grumpy Editor's guide to surviving the systemd debate
The Grumpy Editor's guide to surviving the systemd debate
Example of SysVinit and SystemD configs
* hnet is the sysvinit script
* hnet.service is the systemd service file