Adding A Custom Built Apache Installation to chkconfig

There’s lots of reasons to steer away from a nicely packaged version of apache. Most recently I needed to do this for a custom build of curl and cAres, but whatever your reason, you’ll find yourself with an apachectrl that’s not quite ready to be used with chkconfig.

The fix is really simple, chkconfig wants to see 2 lines in your apachectrl that tell it what it is and what to do with it. At that point, chkconfig will recognize the service as your script name. So here it is:

1. Add the following lines to the top of the apachectrl script that you’ll find in the apache2/bin directory of your install.#!/bin/sh
   #
   # chkconfig: 35 85 15
   # description: Apache is a World Wide Web server.
   #
   # Licensed to the Apache Software Foundation (ASF) under one or more

   The first line:
   # chkconfig: 35 85 15
   The 35 tells chkconfig you want the service running at run level 3 and run level 5.
   The 85 is the start priority.
   The 15 is the stop priority.

   The second line:
   # description: Apache is a World Wide Web server.
   This is merely a description of the service.
   *note* Both lines start with a comment “#” (pound sign).

2. Once your lines are in place you can move or link your apachectrl to /etc/init.d/httpd
3. Once the script is in /etc/init.d/ you can run the following command to make it all go:
   chkconfig httpd on(this is of course assuming that you named the script in /etc/init.d/ “httpd”, if you named the script “chuck” then you’ll run: chkconfig chuck on, I think you get the point).

That is all.

Related Posts:

• No Related Posts