Here's what I did to rebuild the rpm:
rpm -ivh qmail-1.03-16.src.rpm
cd /usr/src/redhat/SOURCES
tar zxvf qmail-1.03.tar.gz
patch -p0 <big-concurrency.patch
Edit qmail-1.03/conf-spawn down to 509 or less so it doesn't blow up because
of the FD_SET descriptor limit
rm qmail-1.03.tar.gz
tar zcvf qmail-1.03.tar.gz qmail-1.03/
rm -rf qmail-1.03
Edit the init script to use multilog instead of splogger if you want
cd ../SPEC
rpm -ba qmail.spec
Then your rpms should magically appear in /usr/src/redhat/RPMS/i386/ I
guess I should've changed the name of the rpm and all that, but it was late
and I was tired. :)
As for the FD_SET problem, Dell sucks and ships a RAID card that requires a
proprietary driver on their so-called "Linux approved" servers. It's a pain
to recompile the kernel with any modifications because that damn module they
have might not work. Everyone keeps pushing them to just release the source
so it can be incorporated into the kernel, but they're being stupid about
it.
Jay
-----Original Message-----
From: James T. Perry [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 19, 2000 4:01 AM
To: '[EMAIL PROTECTED]'
Subject: Re: concurrency remote patch
Hi Jay,
"Austad, Jay" wrote:
>
> I grabbed the source rpm and just applied the patch to it and
> rebuilt it. Works great.
Congrats!
Please teach me how you did it!
> Except, FD_SET is limited to 1024 descriptors.
Don't you hate it when that happens? ;)
> How do I change this? I assume I can't just echo something into
> /proc... I want to be able to do more than 509 concurrency.
I did succeed to raise the concurrency level to 1000,
but its an unofficial "dirty hack" and I can't be liable
for any damages but here's what I did:
(BTW, I am thinking of writing up a mini-howto)
This was originally posted to the qmail list at about
Mon, 18 Sep 2000 20:36:09 +0900 with the title :
Re: conf-spawn and FD_SET SUCCESS!
but updated a little since I forgot to include some
more info.
Warning/Disclaimer:
This worked for me. I am not responsible if something breaks,
or causes any damage to everything or anything related to the
person following the steps below to modify their system and/or
qmail setup (or whatever...).
This was originally posted to the qmail list at about
Mon, 18 Sep 2000 20:36:09 +0900 with the title :
Re: conf-spawn and FD_SET SUCCESS!
but updated since I forgot to include some more info.
linux kernel 2.2.17
qmail-1.03
procmail rc file
(install was accomplished by closely following lwq :)
plus localtime, DNS, big-todo, big-concurrency patches
in that order
changes in qmail configuration:
$qmailhome/control/concurrencylocal 500
$qmailhome/control/concurrencyremote 500
$qmailsrc/conf-spawn set to 1000
$qmailsrc/conf-split set to 100
$qmailsrc/conf-cc set to cc -O2 -D__FD_SETSIZE=2048
ucspi-tcp-0.88
daemontools-0.70
1. Inside the big-concurrency patch:
it said to modify
"/usr/src/linux/include/linux/tasks.h
NR_TASKS from 512 to e.g. 2048"
- directly quoted - which I did.
2. As P.Y. Adi Prasaja mentioned:
raised the __FD_SETSIZE value in
/usr/include/bits/types.h
from 1024 to 2048
3. Just to be sure:
raised the __FD_SETSIZE value in
/usr/src/linux/include/linux/posix_types.h
from 1024 to 2048
4. As Peter van Dijk mentioned:
added -D__FD_SETSIZE=2048 to $qmailsrc/conf-cc
5. Edit the following:
$qmailhome/control/concurrencylocal 500
$qmailhome/control/concurrencyremote 500
$qmailsrc/conf-spawn set to 1000
$qmailsrc/conf-split set to 100
$qmailsrc/conf-cc set to cc -O2 -D__FD_SETSIZE=2048
6. make setup:
bingo!
no compile errors.
qmail is idling ok.
7. Change sources back to default value:
(incase I break something ;)
/usr/include/bits/types.h
/usr/src/linux/include/linux/posix_types.h
both back to 1024
#---------#---------#---------#---------#---------#---------#---------#
-- If somebody can help create a search engine for my room,
I will call them a Saint...
GUI == Graphical User Interference
