[kforge-dev] Ticket #75 (Renaming a service does not trigger a rebuild of apache config) created
John Bywater
john.bywater at appropriatesoftware.net
Mon Oct 19 15:28:16 UTC 2009
Rufus Pollock wrote:
> 2009/10/19 John Bywater <john.bywater at appropriatesoftware.net>:
>> Hi Rufus,
>>
>> I couldn't reproduce this error with kforge-0.17. As Apache config
>> rebuild/reload on service updates is something I've added recently, I
>
> v0.16 so the latest version may fix this.
Great, yes it's fixed. so I'll close the ticket.
>
>> wondered which version you were using when this happened? And whether
>> www.reload_apache was set in kforge.conf?
>>
>> http://knowledgeforge.net/kforge/trac/browser/trunk/src/kforge/plugin/apacheconfig.py
>
> The way I've got it is that apache config is rebuild but reloading is
> carried by a separate system (monit) as this simplifies permissions.
Okay, when the www.reload_apache isn't set, there is a status message
for services to wait for the server to reload, which goes away after
24hrs. There's a more refined message when www.reload_apache is set, but
if the reloading were better detected, the status could be improved.
John
>
> Rufus
More information about the kforge-dev
mailing list