Re: Running Apache in Single Process Mode for Docker Container?

[Yehuda Katz <yehuda@xxxxxxxxxx>]

You could try starting the service and run "ps auxf | grep apache".

This doesn't always give you all the information, but it could help.

- Y

On Sun, Oct 25, 2015 at 10:26 PM, David Aronchick <aronchick@xxxxxxxxx> wrote:

Thank you, this is very helpful! Is there any way to get an output of all the items on the command line ultimately used by apachectl? For example, when I do the following, it fails - I assume I'm missing something.

$ source /etc/apache2/envvars
$ /usr/sbin/apache2 -f /etc/apache2/sites-available/rails.conf  -DFOREGROUND -DNO_DETACH 
AH00534: apache2: Configuration error: No MPM loaded.

On Sun, Oct 25, 2015 at 5:03 PM, Kurtis Rader <krader@xxxxxxxxxxxxx> wrote:

On Sun, Oct 25, 2015 at 3:55 PM, David Aronchick <aronchick@xxxxxxxxx> wrote:

Is it possible (or inadvisable) to run apache using the /usr/sbin/apache binary directly? Is there any significant production issues that might arise?

Run the binary directly as opposed to what? If you mean via apachectl or a /etc/init.d script all they do is invoke the httpd binary directly the the appropriate arguments (e.g., converting "configtest" into "-k"). On UNIX systems there really isn't any difference as far as the kernel is concerned whether you're running a script or a binary. If you choose to invoke the httpd binary directly without the aid of a wrapper script it simply becomes your responsibility to pass all necessary and appropriate arguments; e.g., -f to specify where the config file can be found.

--

Kurtis Rader

Caretaker of the exceptional canines Junior and Hank