[MacPorts] #36101: apache2 @2.2.22_2 startup item

[MacPorts]

#36101: apache2 @2.2.22_2 startup item
----------------------+--------------------------
  Reporter:  grrr@…   |      Owner:  ryandesign
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.1.2
Resolution:           |   Keywords:  mountainlion
      Port:  apache2  |
----------------------+--------------------------

Comment (by paxperscientiam):

 Hello @alphanull, I want to add that I see the same anomalous behavior.


 My /opt/local/etc/apache2/httpd.conf has the directive `Include
 /Users/<user>/server-config/httpd.conf`

 That include in turn has the directive `Include /Users/<user>/server-
 config/httpd-vhosts.conf`.

 As in your experience, `sudo port load apache2` fails to start `httpd`.
 However, when I comment out `Include /Users/<user>/server-
 config/httpd.conf`, `sudo port load apache2` successfully starts `httpd`.

 I did a quick test to see if this might have something to do with
 including configs outside of Server Root -- it may. I replaced `Include
 /Users/<user>/server-config/httpd.conf` with `Include
 etc/apache2/test.conf` and it worked, though I had to kill running `httpd`
 processes before `sudo port load apache2` and `sudo port unload apache2`
 would work again.

 The test.conf file was owned by "root:staff" when I created it. I then
 changed it to "<user>:admin" and still the load/unload commands work.

 It's looking like this bug(?) has to do with whether the includes are
 outside of the server root. Not sure if this is the case. Hope this helps
 us get closer to a solution!

-- 
Ticket URL: <https://trac.macports.org/ticket/36101#comment:16>
MacPorts <https://www.macports.org/>
Ports system for macOS