I have found that apache is much more resource-hungry when it is running RT
(having Mason and the like loaded up in each running instance I’m sure has
something to do with that).
The way I got around having these resource-hogging httpd’s running all my
webpages was simply to run apache on a different port for RT. So, I keep
two seperate config files, I setup a virtualhost called rt.domain.com and it
redirects the user to rt.domain.com:88/rt2/ – works great. This way, I
don’t have all the RT stuff in my virtualhosting httpd and it also makes it
really easy to move it off to its own server in the future (just change
rt.domain.com to point to the new address).
Just some food for thought…
Trevor Sky Garside
email@example.comFrom: “Martin Hemmings” firstname.lastname@example.org
To: “rt-users-list” email@example.com
Sent: Thursday, August 09, 2001 10:29 AM
Subject: RE: [rt-users] Apache/Mason install notes
Ok… sorry for all the posts, I like hearing other people’s ideas before
making changes to stuff in case I’m doing things wrong.
I have finally gotten everything to work after almost 3 days of work. I
a virtual host with a seperate IP configured on the server which got me
RT interface up and running but still had messed up images and links. I
finally got rid of the virtual hosts and just went with an alias to make
Here’s my new config options from httpd.conf
Alias /rt2 “/usr/local/rt2/WebRT/html”
and from config.pm
$WebPath = “/rt2”;
$WebBaseURL = “http://192.168.10.1:80”;
Now I can access RT2 from http://192.168.10.1/rt2 perfectly. Thanks for
help everyone, now I’m off to begin user configuration.