Add lots of unique tags to error log messages

suEXEC: Add Suexec directive to disable suEXEC without renaming the binary (Suexec Off), or force startup failure if suEXEC is required but not supported (Suexec On). Change SuexecUserGroup to fail startup instead of just printing a warning if suEXEC is disabled. Additionally, ap_unixd_config.suexec_disabled_reason has a message, suitable for logging/messaging, explaining why the feature isn't available.

Use the new APLOG_USE_MODULE/AP_DECLARE_MODULE macros everywhere to take advantage of per-module loglevels

unixd_config->ap_unixd_config renames for mod_suexec Submitted By: Dan Poirier Reviewed By: covener

Remove all references to CORE_PRIVATE.

If you study all of the directive implementations, you'll note that we get less than 20% of the NOT_IN_LIMIT rules correct. <Limit > works in about 4 directive contexts and yet, we ignore this fact for 100's of directives. Simply eliminate this nonsense in anticipation of a 100% solution.

update license header text

Update the copyright year in all .c, .h and .xml files

No functional change: remove "internal" tab spacing/formatting.

Update copyright year to 2005 and standardize on current copyright owner line.

fix name of The Apache Software Foundation

apply Apache License, 2.0

update license to 2004.

finished that boring job: update license to 2003. Happy New Year! ;-))

Fix the rest of the apr_pool_userdata_setn() bogosity w.r.t. DSO modules. It's totally unsafe to use apr_pool_userdata_setn() in the post_config phase of a module, since on some platforms when the DSO gets reloaded between phases, the data segment will be at a different address on the second phase and the userdata_get() call will fail. PR: 9413 Submitted by: Tsuyoshi Sasamoto <nazonazo@super.win.ne.jp>

stop using APLOG_NOERRNO in calls to ap_log_[pr]error()

Fix suexec invocations from userdir - the ~ was not being prepended to the uid per our convention. Therefore, bad things would happen (like we wouldn't cd to the right directory). Add a flag to the ap_unix_identity_t structure to indicate if we are in a userdir - if so, prefix the ~. (Modified by Justin, but Colm's patch pointed me in the right direction.) PR: 7810 Submitted by: Colm <colmmacc@redbrick.dcu.ie> Reviewed by: Justin Erenkrantz

Update our copyright for this year.

Only let the "suEXEC enabled" message be printed once, even when we have a DSO that goes through the load-unload-load cycle. Suggested by: Ryan Morgan <rmorgan@covalent.net>, Cliff Woolley

Add back in the "suEXEC mechanism enabled (wrapper: /path/to/suexec)" message that we had back in apache-1.3 and is still scattered throughout our docs. Unfortunately, when mod_suexec is a DSO we're going to get this thing twice in our logs. I believe as a side effect of the load-unload-load cycles of our DSOs we're losing the static data segment, which is where the "didn't we already report this" flag lives.

Update copyright to 2001

Clean up the cgid module now that it supports suexec.

Get mod_suexec compiling on FreeBSD again

The big change. This is part 3 of the apr-util symbols rename, please see the first commit of srclib/apr-util/include (cvs apr-util/include) for the quick glance at symbols changed.

Provide apr_pool_t arg to register_hooks, since anything they do in that step -must- be done with a pool that will not outlive the cmd pool, from which they may have been dynamically loaded.

Remove a couple more NULL handler specifications.

Make mod_cgi and mod_include work when compiled as DSO's again. This is accomplished by moving suexec out of it's own file and into unixd.[ch]. The problem was that suexec.c wasn't being linked into the server unless a module was actually using ap_os_create_process. This is still not clean, but it works now.

Fix a const problem.

Add back suexec support.