Thanks Rainr.
I build the modules in the end with apxs -i -c mod_qos.c -lcrypto
-lpcre because configure asked for items I could not find in my
repositories.
It build this in /etc/httpd/modules/mod_qos
-rw-r--r-- 1 root root 744576 Aug 18 11:37 mod_qos.o
-rw-r--r-- 1 root root 276 Aug 18 11:37 mod_qos.lo
-rw-r--r-- 1 root root 0 Aug 18 11:37 mod_qos.slo
-rw-r--r-- 1 root root 936 Aug 18 11:37 mod_qos.la
And put a compiled .so in :
# ls -l /usr/lib64/httpd/modules/mod_qos.so
-rwxr-xr-x 1 root root 518232 Aug 18 11:37
/usr/lib64/httpd/modules/mod_qos.so
:)
Added to httpd.conf
LoadModule qos_module /usr/lib64/httpd/modules/mod_qos.so
Unsure for the conf file. I've created a file called mod_qos.conf in
/etc/httpd/conf.d/ and added:
## QoS Settings
<IfModule mod_qos.c>
QS_LogOnly on # put mod_qos into a permissive mode. No actions are
applied.
# handles connections from up to 100000 different IPs
QS_ClientEntries 100000
</IfModule>
Does the last configuration step look correct?
Thanks.
Kind regards,
Sophie
--
Sophie Loewenthal
System Engineer ITOPS / Trimble Transport & Logistics
GSM:+32.471.900703
On 8/18/2015 11:36 AM, Rainer Jung wrote:
Am 18.08.2015 um 09:59 schrieb Sophie Loewenthal:
Hi,
I've been trying to build the module mod_qos on for Centos 6 and
wondered if somebody had some experience with this.
The documentation referred to a file buildconf but I did not find this
in the tarball mod_qos-11.16.tar.gz. Does anybody know where I could
find the *buildconf* file?
Install guide read:
tar xfz httpd-2.2.27.tar.gz
tar xfz mod_qos-11.16-src.tar.gz
ln -s httpd-2.2.27 httpd
cd httpd
mkdir modules/qos
cp ../mod_qos-11.16/apache2/* modules/qos
./*buildconf*
./configure --with-mpm=worker --enable-so --enable-qos=shared
--enable-ssl --enable-unique-id
make
cd ..
This creates a DSO module that can be loaded into the Apache server
using the following directive:
LoadModule qos_module <path to module>/mod_qos.so
Typically a script named buildconf or similar is only needed for the
people doing a release. It uses thr auto-tools (autoconf etc.) to
generate the configure script.
If you have a real release tarball, configure should be already
included and you don't need to run buildconf. Just start with the next
step, running configure.
Regards,
Rainr
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
