The Upstart equivalent of chkconfig is the update-rc.d. There's some info on how to use it in the UbuntuBootupHowto linked in L. D. James's answer.
Admittedly, this tool is anything but friendly; it tends to expose the ugly underbelly of SysV init with all it's gory runlevel and priority blackmagic. I have almost never managed to get it to do what I want in the first go. chkconfig did a fantastic job of abstracting all those numbers away and providing a simple, usable interface that was loved by all. Nevertheless, it was always lipstick on a pig.
It's a brave new world and I would suggest you put in some time towards learning how Upstart works so that you can wire new jobs using that. For existing packages/applications that still provide you with SysV init scripts, update-rc.d should allow you to do everything that chkconfig did, except for one usecase. update-rc.d provides no clean way to see what the current status of a given service is, i.e., there is no equivalent of chkconfig --list. For this particular case, I'd suggest ls -l /etc/rc*.d/*${service_name}.
Update: 28-July-2013
Hmm... it appears that the OP has already answered here (https://askubuntu.com/a/277732/111294) suggesting sysv-rc-conf. Can't see how I missed that, have upvoted that answer now.
on 13.10, none of the above 'solutions' work. Ran sysv-rc-conf, update-rc.d. Nada. sysv-rc-conf says bluetooth is off but it still runs. meh
Says it has been converted to upstart but nothing on how to disable the daemon, where the configuation for upstart is, etc, etc.
So, digging around, you can edit /etc/init/bluetooth.conf and just comment things out, presumably only the following is necessary (though I commented anything that looks relevant):
# exec /usr/sbin/bluetoothd
This will probably break with an upgrade but at least the bloody thing is off for a while.
Jobservice, along with jobs-admin is a GUI based tool for handling some upstart scripts if that is your preference. It can be installed from the software center or by running sudo apt-get install jobservice jobs-admin from a terminal.
If I recall, there did not appear to be an easy way to add new jobs from the GUI.
Well, there is some history behind. chkconfig is connected with UNIX System V or SysV (pronounced: "System Five").
Since then, Ubuntu switched to Upstart, and then again it switched to systemd.
systemd uses systemctl which reflects what was chkconfig to SysV.
From the man page :
systemctl may be used to introspect and control the state of the "systemd" system and service manager. Please refer to systemd(1) for an introduction into the basic concepts and functionality
this tool manages.
sysv-rc-conf is an alternate option for Ubuntu.
The usage is almost the same.
To install:
To configure apache2 to start on boot
equivalent chkconfig command
To check runlevels apache2 is configured to start on
equivalent chkconfig command
The Upstart equivalent of chkconfig is the update-rc.d. There's some info on how to use it in the UbuntuBootupHowto linked in L. D. James's answer.
Admittedly, this tool is anything but friendly; it tends to expose the ugly underbelly of SysV init with all it's gory runlevel and priority blackmagic. I have almost never managed to get it to do what I want in the first go. chkconfig did a fantastic job of abstracting all those numbers away and providing a simple, usable interface that was loved by all. Nevertheless, it was always lipstick on a pig.
It's a brave new world and I would suggest you put in some time towards learning how Upstart works so that you can wire new jobs using that. For existing packages/applications that still provide you with SysV init scripts, update-rc.d should allow you to do everything that chkconfig did, except for one usecase. update-rc.d provides no clean way to see what the current status of a given service is, i.e., there is no equivalent of
chkconfig --list. For this particular case, I'd suggestls -l /etc/rc*.d/*${service_name}.HTH
Update: 12-June-2013 The answer at https://askubuntu.com/a/161893/111294 points to a more palatable alternative- sysv-rc-conf.
Update: 28-July-2013 Hmm... it appears that the OP has already answered here (https://askubuntu.com/a/277732/111294) suggesting sysv-rc-conf. Can't see how I missed that, have upvoted that answer now.
chkconfig is a redhat-ism. In Ubuntu we use upstart instead of sysvinit as used by redhat.
on 13.10, none of the above 'solutions' work. Ran sysv-rc-conf, update-rc.d. Nada. sysv-rc-conf says bluetooth is off but it still runs. meh
Says it has been converted to upstart but nothing on how to disable the daemon, where the configuation for upstart is, etc, etc.
So, digging around, you can edit /etc/init/bluetooth.conf and just comment things out, presumably only the following is necessary (though I commented anything that looks relevant):
# exec /usr/sbin/bluetoothd
This will probably break with an upgrade but at least the bloody thing is off for a while.
As of 12.04, chkconfig could be installed using
sudo apt-get install chkconfig.I would recommend using Upstart.
Jobservice, along with jobs-admin is a GUI based tool for handling some upstart scripts if that is your preference. It can be installed from the software center or by running
sudo apt-get install jobservice jobs-adminfrom a terminal.If I recall, there did not appear to be an easy way to add new jobs from the GUI.
Else install chkconfig from Debian packages pool :
https://packages.debian.org/sid/chkconfig
Well, there is some history behind.
chkconfigis connected with UNIX System V or SysV (pronounced: "System Five").Since then, Ubuntu switched to
Upstart, and then again it switched tosystemd.systemdusessystemctlwhich reflects what waschkconfigtoSysV.From the man page :