Why is Apache not tied-up to Upstart?

Most servers I’ve installed on my Ubuntu 10.10 is controlled to start at boot (or during desired events) by upstart except for Apache. Why is it like that? MySQL will not work with BUM or chkconfig because that is the old way of controlling services. So does SSH (server) and a whole lot more. If you want to see what services are under upstart you can view /etc/init.

As I’ve already written in a previous post. If you don’t want these services to start at boot-up, remove/or comment a few lines from its corresponding .conf file in /etc/init.

For example, for CUPS not to start on boot or any other trigger, comment/remove the following lines at the top of its /etc/init/cups.conf file as shown below (in yellow highlight):

# cups - CUPS Printing spooler and server

description     "CUPS printing spooler/server"
author          "Michael Sweet <msweet@apple.com>"

#start on (filesystem
#          and (started dbus or runlevel [2345])
#          and stopped udevtrigger)

stop on runlevel [016]

And why does upstart not have a functioning GUI app to make management easier? I found a recommended app named jobs-admin* but after install it didn’t work. I tried to start it manually from the console only to be greeted by a lot of errors. Note that I am using a freshly installed Maverick Meerkat. jobs-admin might be working properly on earlier Ubuntu versions or when Meerkat has been fully updated.

Do you know of an alternative and working GUI app that can be used to easily manage upstart-based services? Let me know.

*jobs-admin (0.8.0-0ubuntu1) is a simple GTK+ utility that allows any administrator to easily configure jobs (services) present on their system. Jobs may be enabled and disabled, started and stopped, and can even provide tweakable settings about services.

Similar Posts:

Notice: This article was published on February 22, 2011 and the content above may be out of date.