I have recently installed SWS 2.0 on RH 5.2. This was a completely new installation on a fresh HD. I didn''t install the base Apache when installing from RH, but relied on the SWS source and binary installations. I am getting the mod_perl error messages too referencing the libperl.c in the httpd.conf file, but apparently changing that to mod_perl.c works, although I haven''t tried it yet. I did need to include suexec and the fastcgi module. Aparently with Apache 1.3.1 it has suexec support, but you need to recompile for it to work. I also am not completely comfortable with DSO yet, so I "think" you can actually compile a module by not recompiling Apache. I noticed that SWS uses mod_ssl for the secure sockets, but I can''t find it anywhere in the source. Is it even possible with the SWS 2.0 distribution to recomplie Apache without loosing the SSL? If recompiling to enable suexec is not necessary, I would be more than grateful to find out how. I did try recompiling Apache with the fastcgi module and then copying the libfastcgi.so file to my existing module library and adding the appropriate LoadModule FastCgi and AddModule lines in my httpd.conf file, but it crashes whenever I try to start httpsd on that line. -- Andy _____________________ Andrew R. Beebe Maine Web Design RR 2 Box 363 A Bridgton, ME 04009 (207) 647-8411 www.datamaine.com
On Fri, 27 Nov 1998, Andrew Beebe wrote:> I am getting the mod_perl error messages too referencing the libperl.c > in the httpd.conf file, but apparently changing that to mod_perl.c > works, although I haven''t tried it yet.Yes, please change it to read mod_perl.c not libperl.c.> I noticed that SWS uses mod_ssl for the secure sockets, but I can''t find > it anywhere in the source. Is it even possible with the SWS 2.0 > distribution to recomplie Apache without loosing the SSL? If recompiling > to enable suexec is not necessary, I would be more than grateful to find > out how.We are not allowed (by our patent license) to distribute the cryptographic portion of the server separately from the web server itself. You will not be able to recompile the apache binary itself. However, in a forthcoming errata release for the secure web server, I am going to turn on suexec support, so it will be available.> I did try recompiling Apache with the fastcgi module and then copying > the libfastcgi.so file to my existing module library and adding the > appropriate LoadModule FastCgi and AddModule lines in my httpd.conf > file, but it crashes whenever I try to start httpsd on that line.Did you recompile the fastcgi module with the apache 1.3.1 headers, or some other version of the apache headers? This is the proper DSO module installation routine. --- -Preston Brown Red Hat Software, Inc. pbrown@redhat.com
> Did you recompile the fastcgi module with the apache 1.3.1 headers, or > some other version of the apache headers? This is the proper DSO module > installation routine.After sending the first message, I realized through some more reading that that is the proper way to install modules now. I''m still learning, but from the man pages, I figured that is what apxs is for. When I try to compile mod_fastcgi.c with apxs using "apxs -c mod_fastcgi.c" however it fails with "/usr/include/apache/buff.h:73: ssl.h file not found". I know I''m probably just missing something easy, but I''ve yet to figure out what. I have the Apache 1.3.1 source and development RPM''s installed from the SWS 2 CD. -- Andy