[Kolab-devel] Make template more modular, store the service to restart in the header

[Gunnar Wrobel]

"Alain Spineux" <aspineux at gmail.com> writes:

> The idea is to be able to add a services to kolab without changing perl code but taking benefice of kolab template.
> This is what I did with a Before Queue Filtering for postfix.
>
> I made my own configuration  template, but a kolabconf don't restart my new service when it update my configuration :-(
>
> It could be useful to change the KOLAB_META tag in templates to include relevant information
> about what to do when the configuration change
>
> Here is the postfix header
>
> KOLAB_META_START
> TARGET=/kolab/etc/postfix/main.cf
> PERMISSIONS=0644
> OWNERSHIP=kolab-n:kolab-r
> KOLAB_META_END
>
> Include something like
>
> SERVICE=postfix
> UPDATE=service:restart
> MESSAGE=Postfix is restarting
>
> or
>
> SERVICE=postfix
> UPDATE=cmd:/kolab/sbin/postfix reload
> MESSAGE=Postif reload its configuration
>
> maybe include a PRIORITY to know in which order to restart all the changed services ...
>
> That could make kolab more "plugins ready" :-)

Did you try to use the header entry "RUNONCHANGE"?

This functionality should be available in Kolab-2.1.

But please submit a bug with your other suggestions. Thanks!

Cheers,

Gunnar

-- 
____ http://www.pardus.de _________________ http://gunnarwrobel.de _

    >> Mail at ease - Rent a kolab groupware server at p at rdus <<

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium