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.
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 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. 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. The top answer on this AskUbuntu article has a good summary as well. http://askubuntu.com/questions/19320/how-to-enable-or-disable-services -Shawn On Thu, Sep 8, 2016 at 9:18 AM, Ken D'Ambrosio <k...@jots.org> wrote: > I believe Ubuntu is perhaps one of the lesser-used distros in GNHLUG > land, but I'm hoping someone here might be able to offer some insight. > > I've got an Openstack install on Ubuntu 14.04 host systems, and after a > hurricane-induced power outage over the weekend, one of our hosts won't > boot -- it fails (seemingly) at loading an Openstack Neutron service. > So, I figure I'll go into /etc/init.d/ and just chmod -x all the suspect > services, see if it boots, and then manually load services. Not so > much; that had zero apparent impact on the services loading. > > So then I did some reading up on Upstart, and found a whole bunch of > places that the services *might* be loading from... none of which seemed > to impact stuff. I currently have the host booted by some serious > cheating (I pulled a disk, went to "manual repair mode" when it whined > about not being able to mount devices, and loaded services from there -- > it completely fails to boot single-user), but how in blazes do I: > > * See what services want to be loaded? > * See *where* they get loaded? > * Load them individually? > > I've found some of the services mentioned in /etc/init/, /etc/init.d/, > /etc/systemd/system/multi-user.target.wants/, /lib/systemd/system/, > /var/lib/systemd/deb-systemd-helper-enabled/ and > /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ . > I tried playing around with most (all?) of those locations, to no avail. > Any insight into what I'm doing wrong would truly be most appreciated. > > Thanks! > > -Ken > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ >
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
