Quote Originally Posted by ckosloff View Post
Respectfully, I have already clarified that my instructions are meant for only a certain kind of systems, I really ignore how other systems work.
There is a thought-process behind the way I explained, mainly the way apache2 defines envvars:
Code:
# envvars - default environment variables for apache2ctl

# this won't be correct after changing uid
unset HOME

# for supporting multiple apache2 instances
if [ "${APACHE_CONFDIR##/etc/apache2-}" != "${APACHE_CONFDIR}" ] ; then
    SUFFIX="-${APACHE_CONFDIR##/etc/apache2-}"
else
    SUFFIX=
fi

# Since there is no sane way to get the parsed apache2 config in scripts, some
# settings are defined via environment variables and then used in apache2ctl,
# /etc/init.d/apache2, /etc/logrotate.d/apache2, etc.
export APACHE_RUN_USER=www-data
export APACHE_RUN_GROUP=www-data
Please, let's not continue beating a dead horse.
This is a friendly remark, please don't take to offense.

CK
No offense. As an avid reader and seeker for success, because each thread is its own issue, others won't know about how or why your system isn't like the vast majority.

As @swguy has pointed out, others may arrive here having experienced a similar issue but the issue may have occurred for a different reason.

Identifying the contributing conditions helps them determine the value of the fix and/or cause of their issue. My posting of the associated information was in furtherance of completing the posting tips as relates to the issue in this thread.

Those that have offered assistance do so voluntarily. Ideally they will continue to do so especially when enough information is made available as directly relates to the posted issue.

It's a lot to consider and from my perspective you've been adventurous in working with the software. I certainly don't want you to be discouraged to seek support. Your extra effort to bound the conditions will get you the needed help a whole lot faster and more effectively to send you off to increase your profit.