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

George Hunt georgejhunt at gmail.com
Mon Nov 25 20:31:53 EST 2013

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:

> 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.
> 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/20131125/9c01d5f5/attachment.html>

More information about the Server-devel mailing list