>We've been customizing the src rpm's available at: > >http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4. >0.1/rpms/ > >and the mod_webapp rpm at: > >http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4. >0.2-b2/rpms/ > >to produce RPM's that our team feels are stable an logically install on >Redhat 7.x. We've done a number of things to them. > >In mod_webapp: > >We fixed a WebAppMount directive placed in the httpd.conf file that was >incorrect (should have been WebAppDeploy).
Thanks, I miss that patch another time. >We also check if ServerName is set in httpd.conf and attempt >to resolve and >add it if it is not. Good >In the Tomcat RPM's > >We moved the install directory back to /var/tomcat/... because >some of our >installers for other software and Location definitions in >Apache http.conf >require it to be there... Warning, the RPM goal is to enable people use differents versions, ie Tomcat 3.3 and Tomcat 4, which are not exclusive and could be used at the same time. So you need in that case 2 differents home /var/tomcat3 and /var/tomcat4. >We also set the default ports back to that of >tomcat 3.2. This makes sense because we never really saw a >reason to run >tomcat 3.2 and 4.0 together on the same machine. We thought if we were >deploying our Software which uses tomcat4.0 it would be the only tomcat >servlet engine running on a machine. But many users asked me to have TC 3.3 and 4.0 at the same time on their boxes to tests applications migration from Servlet 2.2/1.1 to 2.3/1.2 >We modified the Permissions on the webapps directory to give >tomcat group >users rights to edit files in it, where the >/etc/rc.d/init.d/tomcat script >didn't provide theses permissions previously. It's bad for security, tomcat shouldn't be allowed to be able to write these files, only logs and works dirs.... >We altered the sleep hack in /etc/rc.d/init.d/tomcat to wait >longer because >the tomcat-apache connector needs more time to stop. This >makes "restart" >work (although somewhat slower). Ok >We tried to do all this while properly updating all the >documentation in the >src and nonarch rpm's. > >Our question is: >Would you like these RPM's to make available via Jakarta? For >us it would be >beneficial if we could point our administrators/installers to >an external >persistent source which we didn't need to maintain for getting >the external >packages (like Tomcat4.0) that are required prior to >installing our projects >packages. You make many usefull modifications, I'd like to put back in the original RPM, but I won't touch the home location or include a potential security with webapps directory. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
