Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I understand that there is a switch from init.d to init in Ubuntu. Init.d was fine for me, but I can see and appreciate the change. I am also incredibly thankful that the config files are not foul XML, like launchd's are. Good ideas.

However, using maverick, I still see an awful lot of stuff in init.d. I had thought that upstart was the way forward. I am certain that upstart + init.d is not as simple as either one alone.

So how do I determine the startup procedure, or where to look for files to control some server?

EDIT: More to the point, I guess I'm asking how does the interaction between upstart and sysvinit work today? I am suspicious of the wiki, much of it seems to be from older versions.

share|improve this question
up vote 0 down vote accepted

So how do I determine the startup procedure

Create file in /etc/init/

or where to look for files to control some server?

In /etc/init/

Getting Started upstart:

share|improve this answer

An article at discusses the transition.

If you don't find a services' control script in /etc/init.d, I assume you'll find it's equivalent(s) in /etc/event.d

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.