Apache 1.3.31

jeffery

jeffery

Verified User
Joined
Jan 13, 2004
Messages
279
Accidentally found out the apache 1.3.31 was released by custom apache.

For what apache is updated, see here.
http://www.apache.org/dist/httpd/CHANGES_1.3

OK, here we start :

1. First go to directadmin custom apache directory
# cd /usr/local/directadmin/customapache/

2. Clean everything
# ./build clean

3. Update Apache
# ./build update

4. Now we need to edit this file :
# vi configure.apache_ssl

Change to this :
#!/bin/sh
OPTIM="-DHARD_SERVER_LIMIT=32768 -DFD_SETSIZE=32768 " \
EAPI_MM="SYSTEM" \
SSL_BASE="/usr" \
PORTOBJFORMAT=elf \
./configure \
--with-apache=../apache_1.3.31 \
--with-ssl=/usr \
--prefix=/etc/httpd \
--exec-prefix=/etc/httpd \
--bindir=/usr/bin \
--sbindir=/usr/sbin \

:wq


5. Now start recompile
# ./build apache_mod_ssl

6. After recompiled, safely restart apache
# service httpd restart



Finished~
If any problem comes out, I will try my best to answer the basic ones...

Cheers,

Jeffery :D
 
jeffery said:
Accidentally found out the apache 1.3.31 was released by custom apache.
Click to expand...
Are you saying that the custom apache script now automatically loads and builds 1.1.31?

If so, then if it doesn't also automatically update configure.apache_ssl that's got to be classified as a bug.

So we need to get this clarified.

Are you saying it does automatically load and configure 1.3.31, but doesn't fix configure.apache_ssl?

Thanks for any clarification.

Jeff
 
Re: Re: Apache 1.3.31

jlasman said:
Are you saying that the custom apache script now automatically loads and builds 1.1.31?

If so, then if it doesn't also automatically update configure.apache_ssl that's got to be classified as a bug.

So we need to get this clarified.

Are you saying it does automatically load and configure 1.3.31, but doesn't fix configure.apache_ssl?

Thanks for any clarification.

Jeff
Click to expand...


Yes, Custom Apache automatically download 1.3.31 and set all thing except the file configure.apache_ssl.

The version no of configure.apache_ssl is 'hardcoded' and so I need to manaully change it. Isn't it classified a bug? :D
 
Thanks for the update..

Did all the changes stated and everything is working fine and updated! :D

Dec
 
dec said:
Thanks for the update..

Did all the changes stated and everything is working fine and updated! :D

Dec
Click to expand...

Yes, including those SSL certificate settings.

It should keep your existing httpd conf(s). ;)
 
thanks, John. I printed it out and will file it with my "update stuff".

Jeff
 
By the way, the configure.apache_ssl script was not updating the apache version number. The update process for apache included removing the configure.apache_ssl file then doing a "./build update" to get the new one. Jeff sent me an email about this so I just added a bit of perl code to replace older version #'s with the current one so the "rm -f configure.apache_ssl" is no longer required during a "build update" for apache.

John
 
DirectAdmin Support said:
By the way, the configure.apache_ssl script was not updating the apache version number. The update process for apache included removing the configure.apache_ssl file then doing a "./build update" to get the new one. Jeff sent me an email about this so I just added a bit of perl code to replace older version #'s with the current one so the "rm -f configure.apache_ssl" is no longer required during a "build update" for apache.

John
Click to expand...

I followed the build script exactly and the version number on Apache is still showing 1.3.29 even though it shows that everything was updated successfully.

I am using Freebsd 4.9
 
i2iweb said:
I followed the build script exactly and the version number on Apache is still showing 1.3.29 even though it shows that everything was updated successfully.

I am using Freebsd 4.9
Click to expand...

Have you restarted your httpd?
 
Ok now that is odd.. I did the same thing (though on 5.2.1) and it worked. Might be weird but instead of ./httpd restart try ./httpd stop and after a few seconds ./httpd start and see what the outcome is.
 
Your problem is all the "Operation not permitted" errors you were getting when it was trying to install ap, apachectl, httpd... You were saying yes to overwrite, but then there was an error about operation not permitted. You need to fix that. Are you doing this as root?
 
Thanks for the info toml, it works now. When I looked more closely at the permissions errors I realized I forgot to unlock some directories that I had locked down. Thanks all for all your help...

Kevin

santacruz# httpd -v
Server version: Apache/1.3.31 (Unix)
Server built: May 26 2004 11:38:11
 
You must log in or register to reply here.
Back
Top