Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Aug 2016 07:32:03 -0700
From:      Patrick Powell <papowell@astart.com>
To:        freebsd-ports@freebsd.org
Subject:   Re: [HEADSUP] extracting LoadModule out of httpd.conf
Message-ID:  <24f9dda5-35b8-e2b3-8be2-168859b73bff@astart.com>
In-Reply-To: <57AB978F.3090800@quip.cz>
References:  <D81A85DB3A820BF76A693B22@ogg.in.absolight.net> <57AB978F.3090800@quip.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
On 08/10/16 14:07, Miroslav Lachman wrote:
> Mathieu Arnold wrote on 08/10/2016 17:42:
>> Hi,
>>
>> It is coming.
>>
>> https://reviews.freebsd.org/D7460
>>
>> constructive comments welcome.
>>
>> I don't think I will do that for Apache 2.2 because it expires at the 
>> end
>> of the year.
>
> I agree that there are problems with LoadModule lines in httpd.conf. 
> Because some modules add / remove or comment / uncomment lines in this 
> file making pkg upgrade painful. So I moved some 3rd party modules 
> configuration in to different included file to solve this issue.
> But I am not sure I we really need to split httpd.conf in to 20, 30, 
> or more little files as proposed in comments in 
> https://reviews.freebsd.org/D7460
> I disagree with "httpd.conf never gets changed by the user" - we are 
> always editing httpd.conf on all our servers. For example Listen to 
> listen only on specified IP, ServerAdmin, CustomLog format and couple 
> of Included *.conf files at the end of the httpd.conf
>
> I cannot agree with splitting httpd.conf in to many small files. 
> Change like this was made for dovecot.conf (24 files in conf.d) and it 
> is lot of pain to find something in this mess or edit more than one 
> thing in one file.
>
> I understand that machine (scripted) editing of one big file is worse 
> than deleting / replacing small files but for us humans one (or a few) 
> files are easily editable than tens of small files.
>
> So... LoadModule can be extracted from httpd.conf (and nothing else).
> I am not sure if it should be one file for all modules or separate 
> files for each module.
>
> Miroslav Lachman
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
>

I plead with the people making this change to update apachectl to list 
the modules that are loaded:

 ># apachectl modules
  ....
  mod_perl ....

And when you update mod_perl and the U&*(()*&U httpd.conf file gets 
mangled and the mod_perl line is removed or
commented out,   you now stand a fighting chance of finding this. With 
the change to itty-bitty files this would
be even more useful.

Just out of curiosity,  how are you going to now deal with temporarily 
commenting out LoadModule entries?


-- 
Patrick Powell                 Astart Technologies
papowell@astart.com            1530 Jamacha Rd, Suite X
Network and System             San Diego, CA 92019
   Consulting                   858-874-6543 FAX 858-751-2435
Web: www.astart.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24f9dda5-35b8-e2b3-8be2-168859b73bff>