"Gavin M. Roy" wrote:
>
> Am running a Dual PII-300MHz 256mem Webserver in production. This box gets
> over 2M hits a day. Base installation was Slackware (3.5 I presume). Runs
> great on 2.0.35, except it locks when the kernel is compiled with SMP
> enabled.
IIRC, 2.0.35 had SMP evilness. schlecht verboten yuck.
> I can compile 2.0.36, it error's out in main.c.
It would be most helpful to know what those errors are.
>I can compile any
> 2.2.x kernel, and was running 2.2.6 since Sunday. But like the 2.2.x
> kernels before it, Apache starts acting really funky. The number of
> processes increase, and it stops accepting connections. Not too good for a
> webserver that does 550K to 600K uniques a day. :( Any suggestions or
> information I could provide for better resolution that running 2.0.35 on one
> cpu?
I ran 2.0.36 SMP via Slackware 3.4 and 3.6. And now i am at 2.2.5
I believe there was a patch for 2.0.36 to get around some egcs problems.
[ I tried to dig up the patch. It was published by florian@suse dot de
but i can't find it. ]
Did you recompile apache after rebooting with 2.2.6?
I also had to rebuild procps and samba when i came up to 2.2.x from 2.0.36
(After that, it would be difficult to go back to 2.0.36)
It also looks like i rebuilt net-tools-1.49 after 2.2.x as well.
dik
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
