Hello,
I use peruser for shared hosting and for me it's crucial that there's as
little as possible that could prevent apache from starting. Consider the
following processor:
<Processor x>
Chroot w
</Processor>
Now if the chroot directory w doesn't exist apache will FAIL to start.
Handling bad configuration as fatal error is very dangerous and you
shouldn't do this in general. In this case I don't see why apache couldn't
simply start as usual but fail all requests using that processor. I don't
see why this check has to be made. And if you really want to check that the
directory exists for convenience, throw a warning. Not a fatal error. You
need to check later anyway as anything could happen to the directory between
reading the configuration and starting up the first child for it.
Please don't handle configuration errors by preventing apache from starting,
and remove this behavior if you have used it elsewhere for other directives.
Thanks
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser
