<div dir="ltr"><div><div><div><div><div>In 14.04, the default init system (PID 1) is upstart. Upstart manages what it calls jobs. It also know how to load "classic" sysvinit scripts for backward compatibility. I wasn't aware of this until googling today, but apparently in 14.04, systemd was available to run alongside upstart via the libsystemd-shim package.<br><br></div>Upstart job definitions are found in /etc/init/. Jobs can use config files, which go in /etc/default/. You can start and stop jobs with "initctl start <job>" and "initctl stop <job>". To disable a job, you create a file called /etc/default/JOBNAME.override with the text, 'manual' in it<br><br></div>Sysvinit is based on shell scripts. The scripts live in /etc/init.d/. The system comes up in given runlevels and what starts or stops in a runlevel is determined by the directories /etc/rc?.d where ? is 0-6 or S. The command update-rc.d is used to start/stop or to enable/disable at boot.<br><br></div>I've never actually seen systemd in a 14.04 system (it's the default init in 16.04 though) and has its own way of doing things as well. For stop/start/status, the 'service' command should invoke the correct underlying service.<br><br></div>The top answer on this AskUbuntu article has a good summary as well.<br><a href="http://askubuntu.com/questions/19320/how-to-enable-or-disable-services">http://askubuntu.com/questions/19320/how-to-enable-or-disable-services</a><br><br></div>-Shawn<br><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 8, 2016 at 9:18 AM, Ken D'Ambrosio <span dir="ltr"><<a href="mailto:ken@jots.org" target="_blank">ken@jots.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I believe Ubuntu is perhaps one of the lesser-used distros in GNHLUG<br>
land, but I'm hoping someone here might be able to offer some insight.<br>
<br>
I've got an Openstack install on Ubuntu 14.04 host systems, and after a<br>
hurricane-induced power outage over the weekend, one of our hosts won't<br>
boot -- it fails (seemingly) at loading an Openstack Neutron service.<br>
So, I figure I'll go into /etc/init.d/ and just chmod -x all the suspect<br>
services, see if it boots, and then manually load services. Not so<br>
much; that had zero apparent impact on the services loading.<br>
<br>
So then I did some reading up on Upstart, and found a whole bunch of<br>
places that the services *might* be loading from... none of which seemed<br>
to impact stuff. I currently have the host booted by some serious<br>
cheating (I pulled a disk, went to "manual repair mode" when it whined<br>
about not being able to mount devices, and loaded services from there --<br>
it completely fails to boot single-user), but how in blazes do I:<br>
<br>
* See what services want to be loaded?<br>
* See *where* they get loaded?<br>
* Load them individually?<br>
<br>
I've found some of the services mentioned in /etc/init/, /etc/init.d/,<br>
/etc/systemd/system/multi-<wbr>user.target.wants/, /lib/systemd/system/,<br>
/var/lib/systemd/deb-systemd-<wbr>helper-enabled/ and<br>
/var/lib/systemd/deb-systemd-<wbr>helper-enabled/multi-user.<wbr>target.wants/ .<br>
I tried playing around with most (all?) of those locations, to no avail.<br>
Any insight into what I'm doing wrong would truly be most appreciated.<br>
<br>
Thanks!<br>
<br>
-Ken<br>
______________________________<wbr>_________________<br>
gnhlug-discuss mailing list<br>
<a href="mailto:gnhlug-discuss@mail.gnhlug.org">gnhlug-discuss@mail.gnhlug.org</a><br>
<a href="http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/" rel="noreferrer" target="_blank">http://mail.gnhlug.org/<wbr>mailman/listinfo/gnhlug-<wbr>discuss/</a><br>
</blockquote></div><br></div>