Following up to myself I am. Firstly, that was Directive3 (not Directive4). Directive3 returns OK. $ bin/apachectl configtest works just fine, no problems. $ bin/apachectl start is where it fails to find the command, looks like in some related child process. It seems to be that the command does not add properly on a child restart (probably calling ap_read_config again). If I can figure out how to get gdb attached, I might be able to provide even more data. ------ Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] >>> The opinions expressed above are entirely my own <<< Compassion will cure more sins than condemnation.
