Perhaps you can educate me on this one Peter.  Why use apachectl at all?
You could write a script outside of the install, that centers around :

/path/to/httpd -f  /path/httpd.conf.name -k  [stop,start,restart]

-ds

----- Original Message ----- From: "Peter N Lewis" <[EMAIL PROTECTED]>
To: <users@httpd.apache.org>
Sent: Tuesday, June 06, 2006 8:29 PM
Subject: [EMAIL PROTECTED] Running multiple httpd daemons


On my server, I run the httpd daemon twice, using almost identical httpd.conf files, one on the main port (the live server) and one on a high numbered port (my working draft). Then I edit the files/configuration of the working draft server, restarting it as necessary. When all changes are in place, I rsync the working files to the live files, update the live server's httpd.conf file (by script, based on the working draft version) and restart the live server.

This all works fine, but one issue I have is running multiple copies. I do this by having two copies of apachectl with different configuration. The problem is, apachectl is really part of the apache install, and so any time it is upgrade, I need to grab a new copy of apachectl and reconfigure the two different versions. In fact, what I do is patch apacheclt by adding:

while [ $# -ne 0 ]
do
        case "$1" in
                --pidfile=*) PIDFILE=`echo "$1" | sed -e 's/^[^=]*=//'` ;;
                --httpd=*) HTTPD=`echo "$1" | sed -e 's/^[^=]*=//'` ;;
                --lynx=*) LYNX=`echo "$1" | sed -e 's/^[^=]*=//'` ;;
                --statusurl=*) STATUSURL=`echo "$1" | sed -e 's/^[^=]*=//'` ;;
                *)
                        break
                ;;
        esac
        shift
done

after the configuration section, and having my own apachectl-live and apachectl-work that just call apachectl with parameters.

Is there a better way to do this without patching or duplicating apachectl, or alternatively, can I request that apachectl be modified to support receiving parameters so that it doesn't need to be patched?

I use 1.3.x, but I checked the latest 2.x source and it looks like apachectl still doesn't receive parameters, although it has a complex data driven chunk of code to generate the config parameters so adding the above code would require understanding that data driven stuff, presumably not hard for whoever maintains it.

Thanks,
   Peter.

--
Check out Interarchy 8, just released.
<http://www.stairways.com/>  <http://download.stairways.com/>

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
  "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
  "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to