> Am 02.02.2018 um 15:25 schrieb Plüm, Rüdiger, Vodafone Group 
> <ruediger.pl...@vodafone.com>:
>> -----Ursprüngliche Nachricht-----
>> Von: Jim Jagielski [mailto:j...@jagunet.com]
>> Gesendet: Freitag, 2. Februar 2018 15:15
>> An: httpd <dev@httpd.apache.org>
>> Betreff: Re: New ServerUID directive
>> Why? If it is designed to not change between restarts then
>> there are much easier ways to be unique, which it kinda
>> already is, considering the actual structs being used.
>> Also, this seems like unnecessary admin overhead for the
>> webmaster... if there is a need for such an ID, httpd should
>> provide for it automagically and not require users to have
>> to config one. It seems like config-file fluff to me, IMO.
> +1. If the current ID used is not meeting our requirements, my first thought 
> would be if we could improve it
> to meet them.

Totally agree that inventing a new Directive is the last resort if we cannot 
find a better solution.

If I understand then concrete case here correctly, the admin makes frequent 
config changes and *wants* the shared memory id to stay the same, so the shm is 
re-used and not cleaned up or re-initialized. And our current implementation 
generates new identifiers much to frequently bc the line-number cheat was made 
to detect config changes?


Reply via email to