This is getting really weird...
Looking up httpd -L:
MaxCPEPerChild (http_core.c)
Maximum amount of CPU time a child can use (rlimit).
Allowed in *.conf only outside <Directory>, <Files> or <Location>
So it is CPE, not CPU?
Ok I gave that a go... `httpd` doesn't complain now, but I despite it
is running, when I try to visit the site in my browser the "child"
dies... this is the last few entries in error_log:
[Tue Sep 2 22:09:08 2008] [notice] Apache configured -- resuming
normal operations
[Tue Sep 2 22:09:08 2008] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Tue Sep 2 22:14:29 2008] [notice] child pid 29398 exit signal
Segmentation fault (11)
[Tue Sep 2 22:14:29 2008] [notice] child pid 23690 exit signal
Segmentation fault (11)
[Tue Sep 2 22:14:30 2008] [notice] child pid 19827 exit signal
Segmentation fault (11)
[Tue Sep 2 22:14:30 2008] [notice] child pid 20595 exit signal
Segmentation fault (11)
[Tue Sep 2 22:14:30 2008] [notice] child pid 22510 exit signal
Segmentation fault (11)
[Tue Sep 2 22:14:30 2008] [notice] child pid 20523 exit signal
Segmentation fault (11)
[Tue Sep 2 22:14:31 2008] [notice] child pid 13631 exit signal
Segmentation fault (11)
[Tue Sep 2 22:15:15 2008] [notice] child pid 8973 exit signal
Segmentation fault (11)
The times it has Seg fault is when I was trying to load a page.
httpd -DSSL doesn't work, it crashed with yet another Segmentation fault.
And this not the first time I try to run a web server, it just been up
there for at least 6 months... how can it just go weird like this?
