Eek! never mind this problem.
Apache is working perfectly.
It seems that the machines use different TOP (linux proces monitor)
versions.
For some strange reason, the lower version top sees the forked processes
of apache as threads. What appears to be one big cpu hogging process is
in reality the apache master processes AND the forked processes combined
together. Since apache 1.3.29 does not support threads (instead it uses
a number of seperate processes) this is a faulty way of displaying
apache procs.
The newer top version displays the processes as seperate processes
(different PIDs, no interproces communication).
So what appeared to be an Apache problem is in reality a problem with
displaying the processes.
--
Jürgen -R-
"I don't know, but I will find out!"
>> Stay informed about: smp apache processes problem