Setup the $APACHE_RUN_DIR and $APACHE_LOCK_DIR directories in runtime

[twang2218]

Fix #250

Signed-off-by: Tao Wang [email protected]

[tianon]

Hmm, when I read through #250, I thought Mutex was simply a mutex on Apache itself to ensure it doesn't run more than once -- reading through https://httpd.apache.org/docs/2.4/mod/core.html#mutex, it sounds like it's actually quite a bit more than that, and controls some inter-process coordination too (especially for modules). 😞 😕

[twang2218]

Ok, back to the original problem, it's because there is no /var/run/apache2/ and /var/run/lock/apache2 directories, so how about we create those directories during the runtime?

I changed my PR to creating and setup permissions on $APACHE_RUN_DIR and $APACHE_LOCK_DIR in apache2-forground:

# setup directories and permissions
mkdir -p /run/lock
for dir in ${APACHE_RUN_DIR} ${APACHE_LOCK_DIR}
do
	mkdir -p ${dir}
	chown -R "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$dir"
done

[twang2218]

ping @tianon

[twang2218]

Any updates?

[tianon]

Before:

$ updog --tmpfs /run php:7-apache
AH00526: Syntax error on line 74 of /etc/apache2/apache2.conf:
Invalid Mutex directory in argument file:/var/lock/apache2

After:

$ updog --tmpfs /run 7ecd801f4282
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.14. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.14. Set the 'ServerName' directive globally to suppress this message
[Thu Jan 26 00:27:51.493503 2017] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.10 (Debian) PHP/7.1.1 configured -- resuming normal operations
[Thu Jan 26 00:27:51.493548 2017] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'