52013-01-14 07:25:26ClintonEbadicat42008-07-07 04:28:03localhostconverted to 1.6 markup32008-06-08 14:43:42BenjaminHellAdded startup script and appropriate cron jobs with k5start (and minor other things)22008-05-25 13:31:08AdamChlipalaFix port request description12008-05-24 11:22:50BenjaminHellThis page describes how to run your own apache HTTP daemon, for example if you have special needs regarding apache modules etc. In the following example an individual apache setup with mod_python is described (as BenjaminHell does it for ).

Get a working apache/mod_python installation (in your home dir), and set up a startup procedure, so that cron starts your daemon when mire reboots. In case the webserver process should crash, apache should be started again, too. The following shell script checks if apache is running and starts it if not (adjust the environment variables in the beginning accordingly): /dev/null` kill -0 $PID 2> /dev/null if (test $? -ne 0); then $K5START -b -- $HTTPD -d $SERVERROOT -DFOREGROUND else exit 0 fi else $K5START -b -- $HTTPD -d $SERVERROOT -DFOREGROUND fi ]]>Save the script in a place like $HOME/bin and use cron to execute this script after reboots and every now and then to check if apache is still up and running (adjust capitalized parts):

Your httpd must be configured so that it listens on a dedicated port. The standard port 80 won't work. We use a firewall to keep track of which ports members are using. Submit a firewall rule request on the portal's security settings page to get ProxiedServer ports. Put a line like this into httpd.conf to configure apache so that it listens on this port only:

Apache needs to know where in the Python path to look for mod_python. You need to add the mod_python location to your PythonPath in httpd.conf: PythonPath "sys.path + ['/afs/hcoop.net/WHEREVER_MOD_PYTHON_IS_INSTALLED']"

Next you need "port forwarding" of http requests for your domain to your own httpd (so that you don't need to use addresses like , but gets "mapped" to port 8880). In the domtool setup for this looks like That should be about all you need...

In our AFS environment apache has to be started through k5start to get the right file permissions. However, as a default, httpd detaches from its parent process after the completed startup. This would make it impossible for k5start to renew AFS tickets for the process. The -DFOREGROUND option prevents apache from doing so, and with -b k5start can take care of the backgrounding instead. If you do not consider this, you may run into "permission denied" problems (see Bugzilla bug 291). CategoryMemberManual