[Server-devel] [XSCE] xsce httpd.conf

[Tim Moody]

I agree that httpd-xs.conf belongs in conf.d.  I also think it should not have any default configurations in it.

So I propose the following:

1) Remove all stock configurations from httpd-xs.conf.j2

2) Remove support for 2.2

3) Modify httpd’s main.yml to put httpd-xs.conf.j2 in /etc/httpd/conf.d

I’m not sure what to do with Listen.  stock 2.4 has Listen 80 and httpd-xs.conf has Listen 0.0.0.0:80, which I take to be functionally equivalent.  I’m not sure that we should be listening on the wan interface, but I guess iptables blocks it anyway.

Can I eliminate Listen 0.0.0.0:80?

Tim

From: George Hunt 
Sent: Monday, November 25, 2013 8:31 PM
To: xsce-devel 
Cc: XS Devel 
Subject: Re: [XSCE] xsce httpd.conf

Tim -- regarding httpd-xs.conf

My memory is that the issue httpd-xs.conf was really trying to address was to set the memory limits, based upon the mount of total memory available -- getting squid, ejabberd, httpd, to share the available memory in an equitable fashion. This seems more like a conf.d type of issue. And I also remember how the roll over from httpd 2.2 to 2.4 caused us upgrade pain that was really self inflicted. I don't think it's a good strategy to take over the base conf file.



On Mon, Nov 25, 2013 at 3:01 PM, Tim Moody <tim at timmoody.com> wrote:

  PREAMBLE

  xsce has an httpd-xs.conf file in /etc/httpd/conf, which is a customized version of httpd.conf.  It gets used because /etc/sysconfig/httpd has a clause OPTIONS= -f conf/httpd-xs.conf.

  Except that in the ansible install /etc/sysconfig/httpd doesn’t get set.

  httpd-xs.conf is definitely needed, because it has a lot of settings not in the stock httpd.conf.  But because it replaces httpd.conf it also has lots of stock settings that are not unique to xsce.

  NOW THEREFORE

  We either need to modify ansible to set /etc/sysconfig/httpd or we need to put httpd-xs.conf into /etc/httpd/conf.d and have in contain only the settings we care about for xsce.  In the first approach we have basically taken ownership of all settings for httpd.  In the latter we have only taken ownership of the settings that are different in xsce, but we could get problems where settings accumulate rather than override (such as listen).

  So what’s the answer?

  btw while we are at it we should clean up the httpd-xs, xs-httpd, xs.conf, etc. proliferation of conf files.

  Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/server-devel/attachments/20131126/f611c497/attachment.html>