Few weeks ago we wrote an article about stopping and starting services in Ubuntu automatically. To read that post, click here.
After writing that post, a commenter pointed out that Boot-Up Manager didn’t work in Lucid. So, if Boot-Up Manager isn’t working for you, then continue reading this post to find a tool that will work great in Lucid.
Getting started:
To get started, go to Applications –> Ubuntu Software Center.
Then search and install ‘sysv-rc-conf’:
After installing, go to Applications –> Accessories –> Terminal, then run the command below:
sudo sysv-rc-conf
Put an X into the run-revel to enable or remove the X to disable a service. Putting an X into the box will automatically start the service in that run level. And removing the X disables it.
I have so far gotten it to work when I put an X into the S column. Any other columns hasn’t worked so far. You could also use the mouse to click into the box. When done hit the ‘Q’ key on your keyboard save.
Enjoy and hope and please come back soon.
![Reblog this post [with Zemanta]](http://3-ps.googleusercontent.com/x/www.liberiangeek.net/img.zemanta.com/reblog_e.png,qx-id=1cad3e25-f53b-46f4-98b3-2ab52d6056ad.pagespeed.ce.NyhL2hRe2T.png)
hi again :)
does this do anything for you that BUM does not? sysv-rc-conf is a ncurses-based tool which access *exactly* the same system (i.e. sysv) that BUM does. Or, put anther way BUM is a GUI version of sysv-rc-conf.
My point on your previous post was that a growing number of Ubuntu services (indeed, the plan is for all of them) have moved to upstart, instead of sysv.
Whilst upstart is clearly a better system, it's still quite young and there is a lack of tools to manage it. If you *do* come across a tool, GUI or otherwise, that can manage upstart (and, ideally, sysv *too*), then I'd certainly be keen to hear about it. But, given the underlying technology, I reckon we're a year or two away still.
just one more quick note: with those jobs that still run on sysv (not, MySQL or SSH for example, which BUM and sysv-rc-conf will list but be unable to change), BUM or sysv-rc-conf will manage them just fine. Until, that is, the package receives an upgrade, and then the rc.d links are all recreated! grrrr……
hi again :)
does this do anything for you that BUM does not? sysv-rc-conf is a ncurses-based tool which access *exactly* the same system (i.e. sysv) that BUM does. Or, put anther way BUM is a GUI version of sysv-rc-conf.
My point on your previous post was that a growing number of Ubuntu services (indeed, the plan is for all of them) have moved to upstart, instead of sysv.
Whilst upstart is clearly a better system, it's still quite young and there is a lack of tools to manage it. If you *do* come across a tool, GUI or otherwise, that can manage upstart (and, ideally, sysv *too*), then I'd certainly be keen to hear about it. But, given the underlying technology, I reckon we're a year or two away still.
just one more quick note: with those jobs that still run on sysv (not, MySQL or SSH for example, which BUM and sysv-rc-conf will list but be unable to change), BUM or sysv-rc-conf will manage them just fine. Until, that is, the package receives an upgrade, and then the rc.d links are all recreated! grrrr……
precisely. isn't there a utility that pulls in service descriptions from every file in /etc/init and then lets you set the “start” line to commented or uncommented (to keep the service's dependencies when it's enabled again)? i have no problem doing it manually myself, but there have to be plenty of people out there that would just like some check boxes to work with.
I entirely agree – Upstart may be the (ahem!) “better” boot manager, but the seemingly total inability to actually DO anything with the friggin’ thing makes it useless as **** on a boar-hog! I really wish I could un-install Upstart and re-install sys-v *without* totally trashing my box.
What say ye?
Jim