Thank you for the sudo rule suggestion and for detailed explanation!<div><br><div>Just one more question, if I use MapCache as fcgi, does this mean that on every request the configuration will be read and parsed ? or the configuration will be kept in memory until a the fastcgi process killed and respawned ?<br>
<br><div class="gmail_quote">On Wed, Feb 22, 2012 at 12:37 PM, thomas bonfort <span dir="ltr"><<a href="mailto:tbonfort@terriscope.fr" target="_blank">tbonfort@terriscope.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Wed, Feb 22, 2012 at 11:22, Pavel Iacovlev <<a href="mailto:iacovlev.pavel@gmail.com" target="_blank">iacovlev.pavel@gmail.com</a>> wrote:<br>
> apache2ctl -k graceful is not really an option for me because I would have<br>
> to give root privileges to my apache/php.<br>
</div>you can create a sudo rule that only allows a user to run apache2ctl<br>
-k graceful without giving full root access.<br>
<div><br>
><br>
> "AFAIK, this isn't possible." I don't know anything about apache modules and<br>
> stuff so the next thing I say may not be applicable or just plain stupid,<br>
> but maybe each process will hold their own copy of configuration so the<br>
> apache process will be able to alter it's configuration upon detection of<br>
> file change. There is certainly that added overhead of "checking last<br>
> modified date" and keeping more copies in memory, but this should not be the<br>
> default behavior.<br>
<br>
</div>afaik, at the request level (which is were the freshness test would<br>
occur), there's no way of freeing the memory that allocated the<br>
initial configuration, and no way of allocating memory for the new<br>
configuration that would live across the upcoming requests.<br>
<div><div><br>
><br>
> On Tue, Dec 6, 2011 at 1:00 PM, thomas bonfort <<a href="mailto:tbonfort@terriscope.fr" target="_blank">tbonfort@terriscope.fr</a>><br>
> wrote:<br>
>><br>
>> AFAIK, this isn't possible. Inside an apache module, the configuration<br>
>> is considered read-only as it is shared between multiple worker<br>
>> threads/processed spawned by httpd.<br>
>><br>
>> apachectl configtest && apachectl graceful will restart the server<br>
>> gracefully, i.e. without aborting ongoing requests, and will load the<br>
>> new configuration for subsequent requests.<br>
>><br>
>> --<br>
>> thomas<br>
>><br>
>> On Mon, Dec 5, 2011 at 23:37, John Taranu<br>
>> <<a href="mailto:jtaranu@firstbasesolutions.com" target="_blank">jtaranu@firstbasesolutions.com</a>> wrote:<br>
>> > Thomas,<br>
>> ><br>
>> ><br>
>> ><br>
>> > Is there a better way force MapCache to reload its configuration script<br>
>> > than<br>
>> > restarting apache? I’m working on an application that will use two<br>
>> > load-balanced web servers running MapCache, all pointing to a single<br>
>> > central<br>
>> > tile repository and a single central .xml configuration file. The<br>
>> > configuration file will occasionally be edited, either with deletions or<br>
>> > additional tilesets. Both web servers need to reload the updated<br>
>> > configuration .xml.<br>
>> ><br>
>> ><br>
>> ><br>
>> > Is it possible to set up MapCache to check if the config file was<br>
>> > recently<br>
>> > updated and, if so, reload the config .xml? It looks like this is<br>
>> > currently<br>
>> > enabled under FastCGI, but not under Apache.<br>
>> ><br>
>> ><br>
>> ><br>
>> > John<br>
>> _______________________________________________<br>
>> mapserver-users mailing list<br>
>> <a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
><br>
><br>
</div></div></blockquote></div><br></div></div>